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
: 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
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,
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:
On 11/1/13 8:52 AM, ext Arthur Barstow wrote:
On 10/31/13 11:52 PM, ext Feras Moussa wrote:
Agreed. Some of the points listed appear to be things already
addressed. Takeshi and I have some feedback on the initial mail, but
will wait and provide thoughts on the proposal instead. Looking
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
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,
...@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
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
On 10/31/13 11:52 PM, ext Feras Moussa wrote:
Agreed. Some of the points listed appear to be things already addressed.
Takeshi and I have some feedback on the initial mail, but will wait and provide
thoughts on the proposal instead. Looking forward to seeing it.
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
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
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
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
-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
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
| 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
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
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
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
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
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
22 matches
Mail list logo
