[Bug 793441] rtsp-stream: client transport is not updated for multicast clients

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=793441

Sebastian Dröge (slomo) <slomo at coaxion.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |slomo at coaxion.net

--- Comment #3 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
(In reply to Patricia Muscalu from comment #2)
> I would like to mention additional problems:
> 
> 1. The public API gst_rtsp_stream_get_multicast_address() has been introduced
> a long time ago, I know, but what's the real intention of this function? The
> server is just sending rtp/rtcp data to the multicast groups. It does not
> have any multicast address itself. Which address is supposed to be returned
> in the shared media case with clients requesting different multicast
> addresses? This question is tightly related to the logic in the
> check_mcast_part_for_transport() function. The function will always fail for
> the multicast clients requesting another transport settings than the first
> multicast client.

It should probably have never been a public function, like many things in
gst-rtsp-server that are public API.

Feel free to deprecate that function and let it continue to return something
useless as it does since the beginning of time :)

> 2. update_transport() function will change ttl-mc value. Do we want to do
> this?
>    I added a FIXME.

What does that mean exactly? The TTL of all multicast clients will be defined
by the latest (or first?) multicast client to join?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.