- From: Rob Manson <robman@mob-labs.com>
- Date: Fri, 01 Nov 2013 16:51:32 +1100
- To: public-webapps@w3.org
Sounds good. Thanks. roBman On 1/11/13 4:43 PM, Feras Moussa wrote: > Yes, WebSockets was missing - I've gone ahead and updated the spec to include it. > > Thanks for sharing the links, the content is well thought out. In particular, your diagram does a good job summarizing some of the key consumers and producers that come to play regarding Streams. I'll review it in detail. > > DataChannels also seem like a possible candidate, although I'm not yet very familiar with them. This can be something reviewed and thought through, and added accordingly. > >> Who is coordinating each group that should get involved? MediaStream for example should be based on the Stream interface and all related streams proposals. > Once we come to a consensus in the WG what Streams look like and their role, we can begin to coordinate what the impact is on other groups. > > Thanks, > Feras > > > ---------------------------------------- >> Date: Fri, 1 Nov 2013 16:05:22 +1100 >> From: robman@mob-labs.com >> To: public-webapps@w3.org >> Subject: Re: CfC: publish WD of Streams API; deadline Nov 3 >> >> Along with WebSockets as Aymeric mentioned...WebRTC DataChannels are >> also missing. >> >> And I think Aymeric's point about MediaStream is important too...but >> there is very strong push-back from within the Media Capture & Streams >> TF that they don't think this is relevant 8/ >> >> Also, here's a couple of links for things I've shared/proposed recently >> related to this. >> >> public message >> http://lists.w3.org/Archives/Public/public-media-capture/2013Sep/0229.html >> >> presentation >> http://www.slideshare.net/robman/web-standards-for-ar-workshop-at-ismar13 >> >> code >> https://github.com/buildar/getting_started_with_webrtc#image_processing_pipelinehtml >> >> >> All thoughts and feedback welcome. >> >> >> roBman >> >> >> On 29/10/13 10:22 PM, Aymeric Vitte wrote: >>> I have suggested some additions/changes in my latest reply to the >>> Overlap thread. >>> >>> The list of streams producers/consumers is not final but obviously >>> WebSockets are missing. >>> >>> Who is coordinating each group that should get involved? MediaStream >>> for example should be based on the Stream interface and all related >>> streams proposals. >>> >>> Regards, >>> >>> Aymeric >>> >>> Le 28/10/2013 16:29, Arthur Barstow a écrit : >>>> Feras and Takeshi have begun merging their Streams proposal and this >>>> is a Call for Consensus to publish a new WD of Streams API using the >>>> updated ED as the basis: >>>> >>>> <https://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm> >>>> >>>> Please note the Editors may update the ED before the TR is published >>>> (but they do not intend to make major changes during the CfC). >>>> >>>> Agreement to this proposal: a) indicates support for publishing a new >>>> WD; and b) does not necessarily indicate support of the contents of >>>> the WD. >>>> >>>> If you have any comments or concerns about this proposal, please >>>> reply to this e-mail by November 3 at the latest. Positive response >>>> to this CfC is preferred and encouraged and silence will be assumed >>>> to mean agreement with the proposal. >>>> >>>> -Thanks, ArtB >>>> >>
Received on Friday, 1 November 2013 05:51:58 UTC