The browser environment also has its own challenges that pose
problems for an embedded signaling state machine. One of these is
that the user may reload the web page at any time. If the browser is
fully in charge of the signaling state, this will result in the loss
of the call when this state is wiped by the reload. However, if the
state can be stored at the server, and pushed back down to the new
page, the call can be resumed with minimal interruption.
To handle refreshes, can save peer connection info in signal server and rehydrate, as suggested by IETF:
http://tools.ietf.org/html/draft-ietf-rtcweb-jsep-03#section-3.4.1
The browser environment also has its own challenges that pose problems for an embedded signaling state machine. One of these is that the user may reload the web page at any time. If the browser is fully in charge of the signaling state, this will result in the loss of the call when this state is wiped by the reload. However, if the state can be stored at the server, and pushed back down to the new page, the call can be resumed with minimal interruption.