Page 1 of 1

http-caching not working as expected with moz plugin

Posted: 25 Apr 2009 22:45
by benow
Heyas. I'm not seeing behaviour as expected with caching in the moz plugin. I'm using 9.9a from the ubuntu repository. When I run vlc from the command line with:

Code: Select all

vlc --http-caching=10000 http://cap:2080/live/stream
(content-type: video/mpeg) it buffers for 10s and plays flawlessly, even over the occasional wifi hiccup. When I try to reproduce the same behaviour with the moz plugin via:

Code: Select all

var vlc = document.getElementById("vlc"); var options=new Array( ':http-caching=20000' ); vlc.playlist.add('/live/stream', null, options ); vlc.playlist.play();
or

Code: Select all

var vlc = document.getElementById("vlc"); vlc.playlist.add('http://cap:2080/live/stream', 'Live Stream', 'http-caching=20000'); vlc.playlist.play();
or

Code: Select all

var vlc = document.getElementById("vlc"); vlc.playlist.add('http://cap:2080/live/stream', 'Live Stream', ':http-caching=20000'); vlc.playlist.play();
I don't see similar buffering happening. By inspecting the state I see the same split-second buffering as if it were not being passed http-caching at all.

Is there an alternate way to specify the http-caching option to the plugin? Has anyone had success with http-caching and the moz plugin?

Thanks!

Re: http-caching not working as expected with moz plugin

Posted: 26 Apr 2009 12:23
by Anatoly_B
"options" don't work in v0.9.9, only in 0.9.8a and previous...
viewtopic.php?f=16&t=58451

Re: http-caching not working as expected with moz plugin

Posted: 26 Apr 2009 22:43
by benow
Well, that sucks. I hope it comes back, 'cause functionality is useful. :roll: Thanks for the reply.

For those who might stumble on this, I found some older .deb's here, but issues with dep's, so it's off to mplayer-plugin for me.

Re: http-caching not working as expected with moz plugin

Posted: 27 Apr 2009 14:17
by thannoy
All option are not denied. In fact, allowed options have now to be explicitely tagged as safe to be usable and as there are many many options, time is needed to flag some more option from time to time.
I think http-cache is safe, I proposed a patch on the mailing list for *-cache options. Maybe it will be ok in next releases.