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

Re: PeerConnection lifecycle/navigation/page reloads

From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 26 Jan 2012 12:48:01 -0800
Message-ID: <CABcZeBMsaDwQfjQDTamBWKoUwm15Uq01KgJbhqpB9rxJSKz1tg@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
Cc: Matthew Kaufman <matthew.kaufman@skype.net>, "public-webrtc@w3.org" <public-webrtc@w3.org>
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?

-Ekr
Received on Thursday, 26 January 2012 20:49:14 UTC

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