[vlc-devel] [PATCH] rtsp: clean up multicast handling

Pierre Ynard linkfanel at yahoo.fr
Tue Dec 14 18:24:33 CET 2010


> > Should I write a proper net_GetMcastHopLimit() function in the core
> > and export it?
> 
> Why do you need an accurate TTL value in the SDP anyhow? This
> information is not much use for the RTSP client. In my opinion, it's a
> protocol design bug.

Okay, I did it another way anyway. If it's useless, do you suggest that
the ttl parameter in the Transport header should be removed altogether?
Or the issue will be moot if we always force the TTL to either 1 or 255?

> In fact, may I suggest we remove support for custom IPv6 hop limit,
> and simplify IPv4 Time-To-Live to a single boolean option (1 or 255)
> across VLC?

I'm afraid that users who purposefully set the TTL to a given value to
control the scope of the stream will miss the option, what would you
tell them?

-- 
Pierre Ynard
"Une âme dans un corps, c'est comme un dessin sur une feuille de papier."



More information about the vlc-devel mailing list