On 7/6/14, Brion Vibber <bvibber(a)wikimedia.org> wrote:
That X-Range header was an experiment me and Faidon
tried for the ogv.js
media player I've been prototyping (Flash fallback version) . We couldn't
get the extra header -- or the regular Range header -- to work through the
varnish layer though, so current code doesn't use it.
What problem did you experience? At first glance, the range header
appears to work for me. (Although whether varnish actually caches
ranged responses is unclear)
Its safe to remove that part from the file.
I'm going to recommend something like DASH streaming to better handle
seeking, dynamic resolution changes, and clean buffering & http cache
friendliness; will put some notes together on that in a bit, probably
months out from prototyping it.
(Long story short, a media stream is divided into small chunks of video or
audio, those get loaded a couple at a time over plain http/https, and the
player stitches them back into a continuous stream - but with the ability
to switch resolution s at, or seek to, any packet boundary without any
partial content stuff.)
That definitely sounds cool.
--bawolff