It seems I am misremembering here - we never got around to implementing it in collective.flowplayer, presumably because all our videos were to end up cached in Varnish. It's not too hard to add though:
1. The view looks for a 'start' parameter in the request. This is an integer indicating how many bytes to seek to in the file. 2. Write the correct Content-Length header (taking account of the flv header and where you have seeked to) 3. Write the flv header, "FLV\x1\x1\0\0\0\x9\0\0\0\x9" 4. Seek to the appropriate position in the file and stream from there. See http://mdounin.ru/hg/nginx-vendor-current/file/1695031dbfed/src/http/modules/ngx_http_flv_module.c for details. Laurence ivan.price wrote: > > Hi Laurence, > > When you say it supports pseudo-streaming, is that Including flv files > that are hosted inside the Plone CMS, and not served directly by apache > / lighttpd / streaming server ? My tests using curl / wget show plone > spits out the same file content regardless of the 'start' and 'end' > parameters when i ask for the movie file.. so i'm not sure how that can > work. > > -i > > > > > > On 23/09/10 4:50 PM, Laurence Rowe wrote: >> collective.flowplayer supports pseudo-streaming of flv files, but nobody >> has >> yet implemented pseudo-streaming of H.264 files - a much more complex >> problem. >> >> Laurence >> >> >> ivan.price wrote: >>> >>> Thanks Dimitris, >>> >>> However i think this doesn't fix my problem unfortunately, the video is >>> already in .flv or .mp4 / .m4v formats, the problem is that the plone >>> http server can only spit out the entire file to the client, it cannot >>> send only portions of the file based on a request range. so to see the >>> end of a 2 hour movie, you need to download the whole thing. The >>> forward-buffering works fine, on a local connection its not such a big >>> problem as by the time you want to see the future its almost all >>> arrived, but for internet connections its not so good. please correct >>> me if i'm mistaken there. >>> >>> all our plone content is actually stored on the filesystem (not in >>> zope-db) so in theory i could get 'creative' and have apache serving it >>> directly after plone checks for permissions, but at this stage its not a >>> serious problem for us and i'd prefer to keep things as standard as >>> possible.. we only have a couple of 'how-to' movies currently. >>> >>> thanks very much for the suggestion tho, it's mentally stored for the >>> future. >>> >>> -i >>> > _______________________________________________ > Product-Developers mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/product-developers > > -- View this message in context: http://plone.293351.n2.nabble.com/collective-flowplayer-pseudostreaming-question-tp5556026p5567236.html Sent from the Product Developers mailing list archive at Nabble.com. _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
