2 ms·
> base64 encode the connection information into a string Doesn't work anymore. Firefox times out the answer offer after very few seconds, which makes sharing
by kaoD 8y ago
> base64 encode the connection information into a string
Doesn't work anymore.
Firefox times out the answer offer after very few seconds, which makes sharing the answer offer asynchronously impractical, which effectively killed serverless WebRTC and in turn killed any interest I had on it (for my side projects I mostly do serverless web apps, as in real serverless, not lambda functions).
- Klathmon 8y agoOuch! That really sucks... Is there a ticket number or blog post or something I can research to learn a bit more about the reasoning behind this change with them?
- kaoD 8y agoNo ticket that I know of. It's mentioned in https://blog.mozilla.org/webrtc/ice-disconnected-not/ https://blog.mozilla.org/webrtc/ice-disconnected-not/ > So every 5 seconds Firefox (version >= 49) sends another binding request no matter if the ICE transport is in use or not, and it expects the other side to reply with a binding response. If it hasn’t received a binding response for 6 consecutive binding requests, in other words no reply within the last 30 seconds, it will give up and mark the transport as failed. This results in switching the ICE connection state to ‘failed‘ and stop sending any packets over that transport.