This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 17596 - Can we have an method fast peerconnection reconstruction?
Summary: Can we have an method fast peerconnection reconstruction?
Status: RESOLVED WONTFIX
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Web RTC Working Group
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-26 08:54 UTC by Yang Sun
Modified: 2012-08-03 23:29 UTC (History)
2 users (show)

See Also:

Attachments

Description Yang Sun 2012-06-26 08:54:42 UTC 
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
Comment 1 Harald Alvestrand 2012-08-03 23:29:57 UTC 
Closing as inappropriate for bugtracker. Please go to the mailing list to discuss the issue.