Part of the solution to (2) depends on where the movie files are
hosted that you are playing with flowplayer.

Once the plone page in which the flowplayer is embedded is itself
loaded, plone isn't really involved any further.  At that point, plone
has done it's job of delivering the javascript and the swf that
constitute the flowplayer instance, and doesn't have any further
responsibility.  If the movie file being played is hosted directly
through an apache server, I don't see why the streaming module
wouldn't "just work".

However, if the movie file is itself _also_ a plone content object,
then Plone is responsible for delivering the movie bytes, and (as you
would expect) wouldn't be exposing the capabilities of any apache
streaming module.


regards,

-David



On Tue, Sep 21, 2010 at 13:29, Ivan Price <[email protected]> wrote:
>
> Hi there,
>
> i have recently installed the very good collective.flowplayer product
> and have a question relating to pseudo-streaming.. the ability to scan
> through a large movie without waiting for the whole thing to download.
>
> i have everything working fine in in our Plone installation.. the
> appropriate files are automatically wrapped in the flowplayer flash
> control and everything is sweet.
>
> My question is regarding pseudo streaming.. I have a separate instance
> of flowplayer (3.2.4) and I have configured our apache web server using
> the H.264 streaming module described here:
>
> http://h264.code-shop.com/trac/wiki/Mod-H264-Streaming-Apache-Version2#Configuration
>
> using my custom player config i can successfully scan through large
> movies like on youtube, but this doesn't work in the
> collective.flowplayer version. I'm guessing this is for 2 reasons;
>
> 1. the pseudostreaming.swf control is not loaded by collective.flowplayer
> 2. the plone HTTP server does not support streaming (fetching content
> from half way through the file) as the apache module i installed is not
> used at all by plone itself. (fyi, in our case, plone is behind an
> apache reverse proxy)
>
> problem 1 i think i can fix with lots of new entries in the
> site_properties sheet for flowplayer, problem 2 is more hard core
> though, and i would not assume is possible. my only reason for writing
> is that i notice there is included the pseudostreaming.swf file in the
> collective.flowplayer product, so maybe someone has done this before ?
>
> i'd appreciate any comments on this, even if it's "never gonna happen"
>
> thanks very much for a great product,
>
> -ivan
>
> ACTED.org
>
> _______________________________________________
> Product-Developers mailing list
> [email protected]
> http://lists.plone.org/mailman/listinfo/product-developers
>
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers

Reply via email to