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

[webrtc-nv-use-cases] Peer Connection and back/forward cache (#56)

From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
Date: Mon, 06 Jan 2020 21:51:26 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-545958490-1578347485-sysbot+gh@w3.org>
aboba has just created a new issue for https://github.com/w3c/webrtc-nv-use-cases:

== Peer Connection and back/forward cache ==
Moved from https://github.com/w3c/webrtc-pc/issues/2346

Current browsers do not add pages that have a live (or connected) peer connection to the b/f cache. It would be interesting to enable this. One possibility is for these connections to simulate connection failure so that, should the page be shown from b/f cache, the application logic would try to restart a connection.

A 'b/f cache', or 'page cache' is used when user is on Page1, navigates to Page2 and then clicks the back button to go back to Page1.
Some browsers will reuse the exact same page to quickly render Page1 in the same state it was.
Page1 will typically receive a pageshow event when being rendered from page cache.
This can also be used when user clicks the Forward button.

Please view or discuss this issue at https://github.com/w3c/webrtc-nv-use-cases/issues/56 using your GitHub account
Received on Monday, 6 January 2020 21:51:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:51 UTC