|
From: Yann <ya...@3i...> - 2002-01-17 21:44:45
|
> Huu, in fact I did that. uristream.c was supposed to read files via HTTP hoops, sorry, I thought it was Jean-Francois cause of your CVS messages ;) > and FTP, but it's not working yet, so I commented the > quicktime_xxx_uristream functions and did not put the uristream.c file in > the CVS. Needs some buffering mechanism I am not sure how to implement > (maybee we'd need a separate thread to get data from the network). I cannot answer your question without looking at your code ... But basically, I agree, we need to create a thread retrieving the data and do all the oqt calls in another and we should have a mechanism to wait for the data if quicktime_read ask for data not already local ... I wonder if some libraries are not already here that could do this for us ... What library do you use ??? > Nothing to do with neater protocols, such as RTP/RTSP, just plain > HTTP/FTP. > However, there are some intersting options in the FTP and HTTP protocols > allowing to ask only a byte-range of a file; that could mean seeking is > possible. We still need buffering, and a file that has data organized in a > stream-like fashion (ie, not a 30 Mb video track followed by a 2 Mb audio > track). > > Tell me if you're interested in this FTP/HTTP video playing, or if we > shouldn't bother about this and concentrate on RTP/RTSP! I think we should clearly begin with ftp/http, and then pass to RTP/RTSP, so yes, don't hesitate to put this files and others into the CVS ... ;) Yann. |