[Bug 23832] New: Requiring that negotiated channels be created on the receiver before any data can be received is problematic for some use cases

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23832

            Bug ID: 23832
           Summary: Requiring that negotiated channels be created on the
                    receiver before any data can be received is
                    problematic for some use cases
           Product: WebRTC Working Group
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebRTC API
          Assignee: public-webrtc@w3.org
          Reporter: martin.thomson@skype.net
                CC: public-webrtc@w3.org

It is currently quite difficult to manage negotiated streams.  These cannot be
unilaterally created.  They depend on signaling.  Some usages require that
streams be created and used very quickly without signaling.  These usages
typically have a fixed configuration for tracks and the receiving end is
typically able to create a data channel when packets start arriving. 
Alternatively, the initial packets could contain hints to the application about
what configuration to apply.  The current API prohibits/prevents this.  That is
bad.

The API should fire an event when packets arrive on an unannounced channel. 
Whether this results in an actual data channel or not is probably up for debate
(I can see several options here).

Remaining silent on the issue as the spec currently does is not acceptable.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

Received on Thursday, 14 November 2013 17:37:17 UTC