- From: Cullen Jennings <fluffy@cisco.com>
- Date: Mon, 27 Feb 2012 10:59:12 -0700
- To: public-webrtc@w3.org
On topic of web sockets.... It seems to me it would be very nice to be abel to use one our Data Channels anywhere that one could use a WebSocket. So if the web sockets interface is going to be re-factored to use AbstractMessenger, then I like how the proposals going but if not, I'd prefer to see DataChannel be defined to implement the WebSocket interface. On topic of yet another signaling channel .... I am not keen on creating a new protocol to run over channel 0 to indicate signaling. We are going to need to be able to signal set up of SCTP in SDP to bring up even the first channel, so I'd like to look at see if we can just use this to set up other channels too. This brings DataStreams inline with MediaStreams in how you add them and such. I'd like to be able to think of Data Stream just like any other MediaStream as much as possible. On the topic of in order creation of Data streams... I'm not a fan of trying to guarantee that if the one sides add streams in a particular order, that order is preserved in how they come out of the callbacks on the far side. I'd rather just use labels to allow the applications on the two sides to keep them straight. On the topic of label collision ... For the apps I want to write, if both sides create something with same label name at same time, I want just one stream created with that label with no extra work for me as an app programer. If I wanted two different streams, I would have created int he labels in a way that did not collide. On setting per messages attributes such as reliable vs non reliable I like that API that Adam proposed where you can really on set attributes on a DataChannel and all the messages in the channel get that.
Received on Monday, 27 February 2012 17:59:41 UTC