[Bug 703158] gst-rtsp-server: identify client of a stream transport

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=703158
  GStreamer | gst-rtsp-server | unspecified

--- Comment #4 from Wim Taymans <wim.taymans at gmail.com> 2013-07-01 09:38:51 UTC ---
> 
> Obviously, I am missing something important.

The GstRTSPClient is just an object handling this particular client connection.
What can happen is this:

 - client connects (gets GstRTSPClient object)
 - client does some things, opens session, starts RTP data transport
 - client closes connection (GstRTSPClient finilizes, RTP transport continues)
 - client connects again, new GstRTSPClient is created, uses session id to
   find previous session info, does some more things on its stream (PAUSE, PLAY
   etc)

So, the Client object does not really model a Client but more like a connection
with a client that comes and goes. This means that a stream can exist without a
GstRTSPClient object.

also, a stream can exist with multiple GstRTSPClient objects when the clients
would use the same session id. It is possible for a client to open multiple
connections and do operations on the session streams from both connections.

Both of these situations are not very common but the data model allows them.

-- 
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.