[streaming] Re: VOD implementation suggestions

[James Pennywise]

That's really how I felt at first too -- VOD servers are about serving
video. But after looking at protocols like RTSP and SIP, I've realized
that most architectures intend to differentiate between the actual video
content and a control protocol for that content. Neither RTSP nor SIP are
shy about pointing this out.

"The Real Time Streaming Protocol, or RTSP, is an application-level
protocol for control over the delivery of data with real-time properties."
-- RFC 2326 (RTSP), Abstract

"This document describes Session Initiation Protocol (SIP), an
application-layer control (signaling) protocol for creating, modifying,
and terminating sessions with one or more participants."
-- RFC 3261 (SIP), Abstract

Of course, that's just my latest realization -- I'm still open to
suggestion.

On Tue, 7 Sep 2004, [iso-8859-1] Rémi Denis-Courmont wrote:

> Le Lundi 6 Septembre 2004 07:10, James Pennywise a écrit :
> > After reading the thread on VOD from a few weeks ago and (quickly)
> > browsing through the source of VLC, I'm left wondering why a VOD
> > server (such as RTSP) shouldn't be implemented as a control module
> > similar to HTTP or Telnet.
>
> HTTP, Telnet, GUIs and other "control" modules really are interfaces to
> control the VLC. A VOD server is not a control interface to me. I
> suppose it should be part of the VLC itself, as vlm is. And then, at
> least one interface, in the form of a control module should be able to
> use the VOD's server.
>
> --
> Rémi Denis-Courmont
> http://www.simphalempin.com/home/infos/cv.shtml.fr
>

-- 
This is the streaming mailing-list, see http://www.videolan.org/streaming/
To unsubscribe, please read http://www.videolan.org/support/lists.html