[MPlayer-dev-eng] A RTP streaming patch for "mplayer"
D Richard Felker III
dalias at aerifal.cx
Thu Apr 11 01:30:46 CEST 2002
On Thu, Apr 11, 2002 at 01:18:36AM +0200, Fredrik Kuivinen wrote:
> On Wed, Apr 10, 2002 at 11:01:49PM +0200, Arpi wrote:
> > > >- do NOT remove the old RTP code (maybe put into #ifdfe and make it optiona
> > > l)
> > >
> > > As I noted above, the old code is very limited, and the new RTP code does
> > > everything that the old code does, but a lot more.
> >
> > yes, but the old code
> > - doesn't need external libs
>
> Why is this a problem? IMHO code reuse is a good thing. If there are
> libraries with suitable licenses we should IMHO use them instead of
> rewriting the same functionality or duplicating the code in the
> mplayer tree.
code reuse is good if the code is good, and if it's clean. however,
requiring the user to install extra libs before compiling mplayer is
not good, it's just a pain. there's a difference in code reuse and
external dependencies.
> > - doesn't need c++ compiler
> > - gpl and "shipped" with mplayer
>
> According to http://live.sourceforge.net/ the LIVE.COM Streaming
> Media libraries are under LGPL so it shouldn't be a problem. (I
> assume the patch is under GPL.)
you didn't address the c++ issue, which is both technically (lots of
systems lack or have broken c++ compiler and/or libs) and
aesthetically nasty. it's good that they're lgpl though -- perhaps
some code from them could be ripped to make a nice c implementation.
rich
More information about the MPlayer-dev-eng
mailing list