- From: <bugzilla@jessica.w3.org>
- Date: Tue, 26 Jun 2012 08:54:40 +0000
- To: public-webrtc@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17596
Summary: Can we have an method fast peerconnection
reconstruction?
Product: WebRTC Working Group
Version: unspecified
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: WebRTC API
AssignedTo: public-webrtc@w3.org
ReportedBy: eric.sun@huawei.com
CC: public-webrtc@w3.org
During multi-parties conference call, we may setup peerconnection with
multi-parties. For example, we may have 8 parties in CC.
If our web page is refreshed, peerconnections with 8 parties will be
reconstructed, and ICE candidates will be collected once more and ICE check
will be carried out once more, it greatly reduce the user expericence due to
long time restoration.
So I suggest that can we have a mechanism for ICE storing in server, to let the
ICE store in server and when web page refresh or communication drop, JS will
fetch the "checked" ICE candidates from server, which will enable fast
restoration.
For example, we can add some parameter in IceCandidateCallback or some else, to
let web app store the ICE candidates for fast restoration, it is optional, web
app may choose implement it or not.
This is just an initial consideration, comments are welcome
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Tuesday, 26 June 2012 08:54:49 UTC