[Live-devel] Closing remote server socket(source) when close detected from remote.

[Heena Sirwani]

I have realized that streaming in interleaved mode and having the state
AWAITING_PACKET_DATA, we use fReadHandlerProc as incomingReportHandler1()
for RTPInterface for rtcp
networkReadHandler1() for RTPInterface for rtp.
But I don't see the remote close event(readSocket returning -1) being
handled here. Am I missing something?


-Heena

On 6 January 2017 at 14:12, Heena Sirwani <heena.sirwani at gslab.com> wrote:

> Hi,
>
> We are currently facing a socket descriptor leak for the source through
> which we stream using live555 as proxy. I was looking for a location where
> sockets are closed for the source. I looked into the networkReadHandler
> callback to check if we close sockets if readSocket returns -1(for
> bytesRead=0), but did not find it there. Am I missing something or the
> place where I am looking is incorrect. Also how are the callbacks
> networkReadHandler and tcpReadHandler used?
>
> Thanks,
> -Heena
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20170106/6f9d4b9c/attachment.html>