[Bug 725313] New: rtspconnection: closed() callback is never called in tunneled mode

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=725313
  GStreamer | gst-plugins-base | git

           Summary: rtspconnection: closed() callback is never called in
                    tunneled mode
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: ognyan.tonchev at axis.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


The closed() callback should be called when the GET channel is disconnected in
tunneled mode but currently it is not. The RTSP watch will also remain but it
will never get dispatched unless there the write source is created and attached
to a context, but that is only the case if there is queued data. One side
effect is that the rtsp-server does not know when a client closes the tunnel
and the RTSPClient object will be leaked.


Previously the closed() callback was called and the RTSP watch removed when the
POST channel was disconnected. This was also wrong and was fixed by this
commit:

commit ebe3530f5177d5b22ab60fc6d00a16281a4caa80
Author: Ognyan Tonchev <ognyan at axis.com>
Date:   Wed Feb 19 13:53:06 2014 +0100

rtspconnection: Remove read child source when POST is disconnected

One solution would be to always create the write source, even if there is no
queued data to be written, and thus be able to detect errors on the output
channel as well.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.