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 13790 - Rename localStreams and remoteStreams to sendStreams and receiveStreams or similar since you may send a stream that is received from one peer to another and then it ends up in localStreams (although it's not local)
Summary: Rename localStreams and remoteStreams to sendStreams and receiveStreams or si...
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard: WebRTC
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-16 10:16 UTC by contributor
Modified: 2012-07-18 18:41 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2011-08-16 10:16:09 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/video-conferencing-and-peer-to-peer-communication.html
Multipage: http://www.whatwg.org/C#interface-definitions-0
Complete: http://www.whatwg.org/c#interface-definitions-0

Comment:
Rename localStreams and remoteStreams to sendStreams and receiveStreams or
similar since you may send a stream that is received from one peer to another
and then it ends up in localStreams (although it's not local)

Posted from: 194.237.142.21
User agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.26+ (KHTML, like Gecko) Version/5.0 Safari/534.26+ Ubuntu/10.10 (2.30.6-1ubuntu5) Epiphany/2.30.6
Comment 1 Ian 'Hixie' Hickson 2011-08-31 23:55:59 UTC 
Well renaming it to sendStream/receiveStreams wouldn't make it any clearer since then you'd have a stream in both lists, so by definition you'd have a sent stream in the received list and vice versa. :-)
Comment 2 Per-Erik Brodin 2011-09-02 16:23:27 UTC 
I don't see a problem in that the stream ends up in both lists, just that a stream can not be local and remote at the same time (although it can be sent and received at the same time).
Comment 3 Ian 'Hixie' Hickson 2011-12-01 23:14:02 UTC 
WebRTC is now done by the public-webrtc@w3.org group.