[FFmpeg-devel] [PATCH] rtsp - alternate protocol

Michael Niedermayer michaelni
Sat Dec 29 17:07:16 CET 2007

On Sat, Dec 29, 2007 at 12:35:57PM +0100, Luca Abeni wrote:
> Hi Michael,
> Michael Niedermayer wrote:
> [...]
> >> Ok. Looking at the rest of the code, I suspect a good solution would be 
> >> something like rtsp://localhost:5454?tcp/test1-rtsp.mpg... And we will 
> >> have to overwrite s->filename for removing the "?..." options that are 
> >> between port number and path.
> > 
> > or just add a field to AVFormatContext specifying the preferred protocol
> Yes, that would work too. And it would be simpler.
> But... Is it a good idea to add a new field to AVFormatContext every 
> time that a format requires some new information, which is not used by 
> other formats? Just trying to evaluate all the possible advantages and 
> disadvantages...

Is rt(s)p really the only thing that has a tcp/udp switch need? Couldnt
mms benefit from it too? And maybe others ...
And the wasted byte in AVFormatContext should be weighted against the
space needed for the code to parse ?tcp/udp. That also isnt usefull for
other (de)muxers ...

> Or maybe we can use a new AVFormatContext's flag? (this would avoid 
> changing AVFormatContext).

A flag is tricky for the current TCP/UDP/UDP_MULTICAST.

Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Opposition brings concord. Out of discord comes the fairest harmony.
-- Heraclitus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20071229/5754f507/attachment.pgp>

More information about the ffmpeg-devel mailing list