where Re: CfC: publish WD of Streams API; deadline Nov 3

2013-11-05 Thread Charles McCathie Nevile
On Mon, 04 Nov 2013 09:52:20 +0100, Domenic Denicola dome...@domenicdenicola.com wrote: As for *where* the work is done, I will be working within the context of the WHATWG to produce this specification. My understanding is that usually the W3C picks some point in time to fork WHATWG

Re: CfC: publish WD of Streams API; deadline Nov 3

2013-11-04 Thread Aymeric Vitte
: CfC: publish WD of Streams API; deadline Nov 3 Yes, with good results, groups are throwing the ball to others... I don't know right now all the groups that might need to be involved, that's the reason of my question. 4 days out without internet connection, usually one email every two weeks

RE: CfC: publish WD of Streams API; deadline Nov 3

2013-11-04 Thread Domenic Denicola
From: Arthur Barstow [mailto:art.bars...@nokia.com] Domenic - Mike Smith mentioned you have worked on a related spec. What is the URL? We are working on a streams specification which addresses the appropriate requirements at https://github.com/whatwg/streams. It is still a work in progress,

Re: CfC: publish WD of Streams API; deadline Nov 3

2013-11-04 Thread Aymeric Vitte
The main difference is that you are explaining in details what you are doing and the current draft does not, I will look more closely and comment, I am not sure the ES style really helps everybody understanding it. Regards, Aymeric Le 04/11/2013 09:52, Domenic Denicola a écrit : From:

Re: CfC: publish WD of Streams API; deadline Nov 3

2013-11-03 Thread Arthur Barstow
forward to seeing it. From: tyosh...@google.com Date: Fri, 1 Nov 2013 12:18:47 +0900 To: ann...@annevk.nl CC: dome...@domenicdenicola.com; art.bars...@nokia.com; public-webapps@w3.org Subject: Re: publish WD of Streams API; deadline Nov 3 OK. There seems to be some

Re: CfC: publish WD of Streams API; deadline Nov 3

2013-11-03 Thread Arthur Barstow
Hi Aymeric, On 10/29/13 7:22 AM, ext Aymeric Vitte wrote: Who is coordinating each group that should get involved? I thought you agreed to do that ;). MediaStream for example should be based on the Stream interface and all related streams proposals. More seriously though, this is good to

Re: CfC: publish WD of Streams API; deadline Nov 3

2013-11-03 Thread Aymeric Vitte
Yes, with good results, groups are throwing the ball to others... I don't know right now all the groups that might need to be involved, that's the reason of my question. 4 days out without internet connection, usually one email every two weeks on the subject and suddendly tons of emails,

RE: CfC: publish WD of Streams API; deadline Nov 3

2013-11-03 Thread Feras Moussa
...@gmail.com To: art.bars...@nokia.com CC: public-webapps@w3.org Subject: Re: CfC: publish WD of Streams API; deadline Nov 3 Yes, with good results, groups are throwing the ball to others... I don't know right now all the groups that might need to be involved, that's the reason of my question. 4

Re: CfC: publish WD of Streams API; deadline Nov 3

2013-11-01 Thread Vic99999
EventSources are missing too 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

Re: CfC: publish WD of Streams API; deadline Nov 3

2013-11-01 Thread Arthur Barstow
it. From: tyosh...@google.com Date: Fri, 1 Nov 2013 12:18:47 +0900 To: ann...@annevk.nl CC: dome...@domenicdenicola.com; art.bars...@nokia.com; public-webapps@w3.org Subject: Re: publish WD of Streams API; deadline Nov 3 OK. There seems to be some disconnect, but I'm fine with waiting for Domenic's

RE: Defining generic Stream than considering only bytes (Re: CfC: publish WD of Streams API; deadline Nov 3)

2013-10-31 Thread Feras Moussa
of Streams API; deadline Nov 3) Hi Dean, On Thu, Oct 31, 2013 at 11:30 AM, Dean Landolt d...@deanlandolt.commailto:d...@deanlandolt.com wrote: I really like this general concepts of this proposal, but I'm confused by what seems like an unnecessary limiting assumption: why assume all

Re: Splitting Stream into InputStream and OutputStream (was Re: CfC: publish WD of Streams API; deadline Nov 3)

2013-10-31 Thread François REMY
Yes, having the InputStream and OutputStream interfaces would be great, and the “Stream” class could inherit from both. The important thing is that an external API can return either a readable or a writable stream, depending on what make sense for it. Since JavaScript does not provide a way

Re: publish WD of Streams API; deadline Nov 3

2013-10-31 Thread Anne van Kesteren
On Wed, Oct 30, 2013 at 6:04 PM, Domenic Denicola dome...@domenicdenicola.com wrote: I have concrete suggestions as to what such an API could look like—and, more importantly, how its semantics would significantly differ from this one—which I hope to flesh out and share more broadly by the end

Re: publish WD of Streams API; deadline Nov 3

2013-10-31 Thread Takeshi Yoshino
OK. There seems to be some disconnect, but I'm fine with waiting for Domenic's proposal first. Takeshi On Thu, Oct 31, 2013 at 7:41 PM, Anne van Kesteren ann...@annevk.nl wrote: On Wed, Oct 30, 2013 at 6:04 PM, Domenic Denicola dome...@domenicdenicola.com wrote: I have concrete suggestions

Re: Splitting Stream into InputStream and OutputStream (was Re: CfC: publish WD of Streams API; deadline Nov 3)

2013-10-31 Thread Takeshi Yoshino
On Thu, Oct 31, 2013 at 4:48 PM, François REMY francois.remy@outlook.com wrote: Since JavaScript does not provide a way to check if an object implements an interface, there should probably exist a way to check that from the API, like: Basically it should be sufficient if each API can

RE: publish WD of Streams API; deadline Nov 3

2013-10-31 Thread Feras Moussa
2013 12:18:47 +0900 To: ann...@annevk.nl CC: dome...@domenicdenicola.com; art.bars...@nokia.com; public-webapps@w3.org Subject: Re: publish WD of Streams API; deadline Nov 3 OK. There seems to be some disconnect, but I'm fine with waiting for Domenic's proposal first. Takeshi

Re: CfC: publish WD of Streams API; deadline Nov 3

2013-10-31 Thread Rob Manson
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

RE: CfC: publish WD of Streams API; deadline Nov 3

2013-10-31 Thread Feras Moussa
-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

Re: CfC: publish WD of Streams API; deadline Nov 3

2013-10-31 Thread Rob Manson
Date: Fri, 1 Nov 2013 16:05:22 +1100 From: rob...@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

RE: publish WD of Streams API; deadline Nov 3

2013-10-30 Thread Domenic Denicola
From: Arthur Barstow [mailto:art.bars...@nokia.com] If you have any comments or concerns about this proposal, please reply to this e-mail by November 3 at the latest. I have some concerns about this proposal, and do not think it is solving the problem at hand in an appropriate fashion. I

Re: CfC: publish WD of Streams API; deadline Nov 3

2013-10-30 Thread François REMY
| If you have any comments or concerns about this proposal, please reply | to this e-mail by November 3 at the latest. While adding streams to the platform seems a good idea to me, I've a few concern with this proposal. My biggest concerns are articulated over two issues: - Streams should

Re: publish WD of Streams API; deadline Nov 3

2013-10-30 Thread Aymeric Vitte
As you mention streams are existing since the begining of times and it's incredible that this does not exist on a web platform, but apparently the subject is still not so easy, node changed its stream quite a lot of time. I probably will not be able to answer back in the coming days but your

Re: CfC: publish WD of Streams API; deadline Nov 3

2013-10-30 Thread Dean Landolt
I really like this general concepts of this proposal, but I'm confused by what seems like an unnecessary limiting assumption: why assume all streams are byte streams? This is a mistake node recently made in its streams refactor that has led to an objectMode and added cruft. Forgive me if this has

Splitting Stream into InputStream and OutputStream (was Re: CfC: publish WD of Streams API; deadline Nov 3)

2013-10-30 Thread Takeshi Yoshino
Hi François On Thu, Oct 31, 2013 at 6:16 AM, François REMY francois.remy@outlook.com wrote: - Streams should exist in at least two fashions: InputStream and OutputStream. Both of them serve different purposes and, while some stream may actually be both, this remains an exceptional

Defining generic Stream than considering only bytes (Re: CfC: publish WD of Streams API; deadline Nov 3)

2013-10-30 Thread Takeshi Yoshino
Hi Dean, On Thu, Oct 31, 2013 at 11:30 AM, Dean Landolt d...@deanlandolt.com wrote: I really like this general concepts of this proposal, but I'm confused by what seems like an unnecessary limiting assumption: why assume all streams are byte streams? This is a mistake node recently made in

Re: CfC: publish WD of Streams API; deadline Nov 3

2013-10-29 Thread Aymeric Vitte
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

CfC: publish WD of Streams API; deadline Nov 3

2013-10-28 Thread Arthur Barstow
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