W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2012

Re: PeerConnection lifecycle/navigation/page reloads

From: Harald Alvestrand <harald@alvestrand.no>
Date: Thu, 26 Jan 2012 22:39:48 +0100
Message-ID: <4F21C824.1000301@alvestrand.no>
To: Eric Rescorla <ekr@rtfm.com>
CC: Justin Uberti <juberti@google.com>, Matthew Kaufman <matthew.kaufman@skype.net>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On 01/26/2012 09:48 PM, Eric Rescorla wrote:
> On Thu, Jan 26, 2012 at 12:45 PM, Justin Uberti<juberti@google.com>  wrote:
>> Right. The PC lifetime is bound to the page, but with JSEP, you can get the
>> new PC back to the same state as the old one by cramming in the session
>> descriptions from the old PC.
> OK, that was my assumption as well.
>
> Maybe a little out of scope of this WG, but do you feel that that's going to
> be the preferred option rather than using a worker to save the PeerConnection
> so you can resurrect it without ICE?
I suspect that some people will try webworkers, so we should make sure 
the semantics of having a PC in a webworker are well-defined. I'm not 
knowledgeable enough about webworkers to know whether we need to do 
anything special to accomodate them.

Reload with server-stored state should work in browsers without 
webworkers, too.
Received on Thursday, 26 January 2012 21:40:27 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:26 UTC