On Wed, Feb 3, 2010 at 6:48 PM, Ross Finlayson wrote:
> Jeremy,
>
> I applied your previous patches (to turn 'nonblocking' mode on, then off
> for the socket if there's a timeout parameter), and it will appear in the
> next release, but I'm not going to apply this one, because synchronous
> (block
Jeremy,
I applied your previous patches (to turn 'nonblocking' mode on, then
off for the socket if there's a timeout parameter), and it will
appear in the next release, but I'm not going to apply this one,
because synchronous (blocking) socket reads in "RTSPClient" will
eventually be going aw
Hi Ross,
Sorry to disturb you again.However,I really need your help.
I try to transmit multiple stream and i read the following text from
the FAQ:
However, when using the "LIVE555 Streaming Media" code, you should be
familiar with event-driven programming, and understand that an ev
I am trying to follow basic flow of events in Dynamic MediaServer sample...
Can someone point me how the "play" event is signaled to RTP sink to
start actual streaming?
Thanks,
-V
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live5
When streaming over TCP, Live555 can deadlock if it loses the connection to
the server for whatever reason (internet goes down, server has a power
outage, LAN fails, etc.). I tracked the deadlock down to
RTPInterface::handleRead:
while ((curBytesRead = readSocket(envir(), fNextTCPReadStreamSo
