Open angrave opened 2 years ago
The current implementation assumes the caption sequence always starts at 1. It could call /closedcaption/seq [GET] upon any failure or at initial (re-)connection.
See protocol and suggestions here-
https://support.zoom.us/hc/en-us/articles/115002212983-Using-a-third-party-closed-captioning-service
Poor connections and disconnects are not handled well. It would be good to some implement retry logic that includes a back off logic.
It would be great if Zoom and Link Encoder can share code; i.e these are just different servers/ procotols that share a lot of the frontend.
The current implementation assumes the caption sequence always starts at 1. It could call /closedcaption/seq [GET] upon any failure or at initial (re-)connection.
See protocol and suggestions here-
https://support.zoom.us/hc/en-us/articles/115002212983-Using-a-third-party-closed-captioning-service
Poor connections and disconnects are not handled well. It would be good to some implement retry logic that includes a back off logic.
It would be great if Zoom and Link Encoder can share code; i.e these are just different servers/ procotols that share a lot of the frontend.