My Verto app currently checks: vertoHandle (to see if Verto has been initialised currentCall.state.name (to see if a call is connected) The problem with this of course is that if the browser is refreshed, those variables are lost and my app is assuming it needs to reconnect (which often, due to the magic of Verto, it doesn't actually need to). So my question is how best to check the session (and call) states? Would, say, loading those variables into the browser's localstorage be a good method, or is there a better way of querying the current sates?
verto communicator stuffs the session id down in local storage for this.
On May 29, 2018, at 2:29 PM, Rick Jarvis <rick@magicmail.mooo.com> wrote:
My Verto app currently checks:
vertoHandle (to see if Verto has been initialised currentCall.state.name (to see if a call is connected)
The problem with this of course is that if the browser is refreshed, those variables are lost and my app is assuming it needs to reconnect (which often, due to the magic of Verto, it doesn't actually need to).
So my question is how best to check the session (and call) states? Would, say, loading those variables into the browser's localstorage be a good method, or is there a better way of querying the current sates?
participants (2)
-
Michael Jerris
-
Rick Jarvis