ISSUE-4: Requiring that negotiated channels be created on the receiver before any data can be received is problematic for some use cases
Requiring that negotiated channels be created on the receiver before any data can be received is problematic for some use cases
- State:
- RAISED
- Product:
- Raised by:
- Martin Thomson
- Opened on:
- 2013-11-12
- Description:
- 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. However, the current API prohibits/prevents this.
- Related Actions Items:
- No related actions
- Related emails:
- Re: ISSUE-4: Requiring that negotiated channels be created on the receiver before any data can be received is problematic for some use cases (from martin.thomson@gmail.com on 2013-11-14)
- Re: ISSUE-4: Requiring that negotiated channels be created on the receiver before any data can be received is problematic for some use cases (from harald@alvestrand.no on 2013-11-14)
- ISSUE-4: Requiring that negotiated channels be created on the receiver before any data can be received is problematic for some use cases (from sysbot+tracker@w3.org on 2013-11-12)
Related notes:
No additional notes.
Display change log
