Closed GoogleCodeExporter closed 9 years ago
The current implementation is a bit of a mess - pseudo-streaming is turned on
by default with "lighttpd" in
the JW Player open ad streamer. JW Player supports the "streamer" flashvar to
allow different streaming
providers to be enabled - see
http://www.longtailvideo.com/support/tutorials/HTTP-Video-Streaming for an
example with MOOV.php
So, the "providers" feature is also required for JW Player to allow specific
streaming providers to be turned on.
But I'm not sure what the correct interpretation of the VAST spec is for this -
is HTTP pseudo-streaming
suppose to be "progressive" or "streaming" in the VAST response?
My interpretation is that:
http:// + "progressive" = progressive
http:// + "streaming" = pseudo-streaming
rtmp:// + "streaming" = rtmp streaming
etc.
This requires changes on the OpenX side as well - both forms of http:// come
down as "progressive" right
now.
Original comment by paul.sch...@gmail.com
on 15 Sep 2009 at 8:06
Moved to critical - related to issue 78
Original comment by paul.sch...@gmail.com
on 15 Sep 2009 at 9:46
Ok, here's the decision:
1. For ads - only http progressive and rtmp streaming support - http
pseudo-streaming is not necessary as
skipping forward in an ad does not make sense
2. For show streams, the "provider" config option will be implemented to allow
different providers to be used
Original comment by paul.sch...@gmail.com
on 15 Sep 2009 at 4:32
Implement providers for JWPlayer - at the moment it's fixed to "lighttpd" for
pseudo-streaming which is limiting
Original comment by paul.sch...@gmail.com
on 25 Sep 2009 at 8:44
Done! See JW player example 39 and flowplayer http-example39
Original comment by paul.sch...@gmail.com
on 6 Oct 2009 at 6:01
Original issue reported on code.google.com by
paul.sch...@gmail.com
on 31 Aug 2009 at 8:05