<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://www.w3.org/Bugs/Public/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4"
          urlbase="https://www.w3.org/Bugs/Public/"
          
          maintainer="sysbot+bugzilla@w3.org"
>

    <bug>
          <bug_id>17596</bug_id>
          
          <creation_ts>2012-06-26 08:54:42 +0000</creation_ts>
          <short_desc>Can we have an method fast  peerconnection reconstruction?</short_desc>
          <delta_ts>2012-08-03 23:29:57 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WebRTC Working Group</product>
          <component>WebRTC API</component>
          <version>unspecified</version>
          <rep_platform>PC</rep_platform>
          <op_sys>Windows NT</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>WONTFIX</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Yang Sun">eric.sun</reporter>
          <assigned_to name="Web RTC Working Group">public-webrtc</assigned_to>
          <cc>harald</cc>
    
    <cc>public-webrtc</cc>
          
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>69394</commentid>
    <comment_count>0</comment_count>
    <who name="Yang Sun">eric.sun</who>
    <bug_when>2012-06-26 08:54:42 +0000</bug_when>
    <thetext>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 &quot;checked&quot; 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</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>71836</commentid>
    <comment_count>1</comment_count>
    <who name="Harald Alvestrand">harald</who>
    <bug_when>2012-08-03 23:29:57 +0000</bug_when>
    <thetext>Closing as inappropriate for bugtracker. Please go to the mailing list to discuss the issue.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>