repeated read requests for video after the processing is finished

DarthVeyda

• September 03, 2018 05:07

After the video has been recorded, verified and processed, the Ziggeo app keeps sending requests to read(?) the video, well, forever (I gave up after ~500 requests or so). At least, I think it's the application, because I can destroy the recorder and that won't have any effect (when I try to destroy the application, the page hangs with endless errors for the same requests). It's literally just reading the video data over and over, like this:

[GET] /v1/applications/*application_token*/videos/*video_token_or_key*

So, my usual questions:

1. What is it that the application is trying to do? A healthcheck polling? The processing doesn't actually end even after embedded recorder said it has been finished? Something else entirely?

2. Is this normal or I'm doing something wrong (if so, how to make it stop?)

We still use v1.27 (that is, local copies of ziggeo.js and ziggeo.css, which, I think, are the end result of compiling the Ziggeo Javascript SDK).

Thanks!

 

0

• 

  Bane

  • September 03, 2018 20:54

  Hi :)

  There should be some read checks to see if video is ready or not. These types of requests would happen as your video is being uploaded, verified and processed and is corresponding with the events that would need these details.

  These are the ones I reference: https://ziggeo.com/docs/sdks/javascript/browser-interaction/events

  The last one that would fire, and which could cause more video request pooling would be the ready_to_play.

  Having that said of course, the same is not available in r27. My suggestion would be to make a quick check on some local page by setting it up with a test against our current stable (r30) or latest (r32).

  This would tell you if the same exists in a later revision.

  * We have made many changes since r27 to r32 and have some in motion for r33 so each revision brings few improvements and sometimes new available events.

  If the same continues, it might be better to create a ticket instead so that you can share a link with us privately allowing us to inspect the specific case and see what might be happening.

  PS: You can just add them as link references, no need to compile it all for a quick test.

  So for example this page would help you get the links with your application setup in few moments: https://ziggeo.com/docs/sdks/javascript/browser-integration/header

  Copy paste it and you are ready to go. Of course please do let us know how it goes.

  Regards,
  Bane

  0
• 

  DarthVeyda

  • September 11, 2018 05:08

  Hi @Bane :)

   

  I've switched to the latest version (v2.32.7), and endless polling is still there. ready_to_play doesn't seem to fire (I've checked the reference - isn't it firing only for a player?)

  0
• 

  Bane

  • September 11, 2018 17:02

  Hi,

  OK, good to know. Can you please let us know if there is a link that we could check to see what is happening?

  * You can send it to our support@ziggeo.com email and just mention this URL for context.

  Also can you recreate that with the resources being pulled over from our website (not using the own version of our scripts)?

  Regards,
  Bane

  0

Please sign in to leave a comment.