[vls-devel] Re: [RFC] VideoLAN Server Architecture For the Future

[Bill Eldridge]

One issue that's been hacked a few times
but not really integrated is the interaction
of ffmpeg, where you can take a vob output
from ffmpeg into a fifo and hack vls not
to seek on the fifo, and thus you're streaming
from ffmpeg's input. THis might be replaced
with a URL for ffmpeg, with a UDP socket input
for vls (& UDP output for ffmpeg and/or ffserver),
etc.

I have a bit of a hacked http.cpp interface
for vls on http://techweb.rfa.org/staff/bill
that only failed because of page buffering
issues (it was cutting off after 512 bytes
on the POST with some browsers but not with
others) that can provide a different kind
of control interface than the telnet.cpp
one.


Jean-Paul Saman wrote:
> VIDEOLAN SERVER
> ===============
> The VideoLAN Server as it currently is lacks some features to become a 
> complete VOD solution or streaming solution. It's input capabilities is 
> way behind the VideoLAN client. Developing all input capabilities for 
> both VideoLAN server and client in duplication is waste of everybody 
> time. It should be possible to combine both solutions in one way or 
> another. Here is the way I think this could be done. Please comment on it.
-- 
Bill Eldridge
Radio Free Asia
bill at rfa.org


-- 
This is the vls-devel mailing-list, see http://www.videolan.org/vls-devel/
To unsubscribe, please read http://www.videolan.org/lists.html
If you are in trouble, please contact <postmaster at videolan.org>