google-code-export / flowplayer-core

Automatically exported from code.google.com/p/flowplayer-core
2 stars 0 forks source link

HTTPStreaming Plugin does not support streamCallbacks #622

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
This issue was initially posted in the flowplayer-plugin project. However, it 
was suggested on the Flowplayer forums to post the issue here. Please see the 
link below to the issue listed on the flowplayer-plugin project.

http://code.google.com/p/flowplayer-plugins/issues/detail?id=43

Original issue reported on code.google.com by mcapor...@gmail.com on 14 Aug 2012 at 2:22

GoogleCodeExporter commented 9 years ago
Need a working demo if possible

Original comment by electrot...@gmail.com on 15 Aug 2012 at 1:49

GoogleCodeExporter commented 9 years ago
If you have a config like this

streamCallbacks: ['onMyStreamEvent', 'onMyOtherStreamEvent'],

outside the clip config in the player config it should configure it fine. 

you can log to see if they are being registered

log: { level: 'debug', filter: 'org.flowplayer.controller.NetStreamClient, 
org.flowplayer.httpstreaming.*' },

both providers are obviouslly different you mention both FMS and Wowza which 
are also obviouslly different are you for certain you have configured it 
correctly for http dynamic streaming ? 

if you log to this  org.flowplayer.controller.* it might tell you if its 
actually being dispatched and it might through an error that the method has not 
been registered. 

Original comment by electrot...@gmail.com on 15 Aug 2012 at 4:42

GoogleCodeExporter commented 9 years ago
I'm working on getting all of the pieces in place for a working demo. I will 
update with examples when complete. 

Original comment by mcapor...@gmail.com on 15 Aug 2012 at 7:56

GoogleCodeExporter commented 9 years ago
You are indeed correct, the callbacks are being fired in the HTTP Streaming. 
The issue was in our initial prototyping I was running loading the web page as 
a file into my web browser. When I moved everything to our webserver in order 
to provide an example to you, it magically started working. I'm going to guess 
that there is a difference in browser security from running a flash on a page 
loaded locally as opposed to loading from a webpage. My apologies for the 
confusion. Please close this issue.

Original comment by mcapor...@gmail.com on 16 Aug 2012 at 1:18

GoogleCodeExporter commented 9 years ago
Oh yes you need to add the location to the sandbox if it's run locally. No 
problem glad that is working. 

Original comment by electrot...@gmail.com on 18 Aug 2012 at 6:35

GoogleCodeExporter commented 9 years ago
ok closing this for now thanks. 

Original comment by electrot...@gmail.com on 20 Aug 2012 at 10:32