On 10/22/14 6:27 PM, Paul Cotton wrote:
given the magnitude of the changes in [changeset], a new WD should be
published.
Can we please wait until after the TPAC week to publish the proposed
Streams heartbeat? Given the substantive changes being made here I
think it would be best to have a
- annevk@, feras.moussa@, domenic@, acolwell@, art.barstow@
23.10.2014, 15:06, Arthur Barstow art.bars...@gmail.com:
On 10/22/14 6:27 PM, Paul Cotton wrote:
given the magnitude of the changes in [changeset], a new WD should be
published.
Can we please wait until after the TPAC week to
On Oct 23, 2014, at 15:10 , cha...@yandex-team.ru wrote:
- annevk@, feras.moussa@, domenic@, acolwell@, art.barstow@
23.10.2014, 15:06, Arthur Barstow art.bars...@gmail.com:
On 10/22/14 6:27 PM, Paul Cotton wrote:
given the magnitude of the changes in [changeset], a new WD should be
, 2014 6:26 AM
To: cha...@yandex-team.ru
Cc: Paul Cotton; Takeshi Yoshino; Jerry Smith (WINDOWS); public-webapps;
public-html-me...@w3.org
Subject: Re: [streams-api] Seeking status of the Streams API spec
On Oct 23, 2014, at 15:10 , cha...@yandex-team.ru wrote:
- annevk@, feras.moussa@, domenic
Hi Arthur,
OK. Since I hurried, there're some odd texts left. Fixed:
https://dvcs.w3.org/hg/streams-api/rev/891635210233
On Tue, Oct 21, 2014 at 10:53 PM, Arthur Barstow art.bars...@gmail.com
wrote:
On 10/14/14 11:06 PM, Takeshi Yoshino wrote:
Not to confuse people, too late but I replaced
...@google.com]
Sent: Wednesday, October 22, 2014 8:38 AM
To: Arthur Barstow
Cc: Paul Cotton; Jerry Smith (WINDOWS); Anne van Kesteren; public-webapps;
Feras Moussa; public-html-me...@w3.org; Domenic Denicola; Aaron Colwell
Subject: Re: [streams-api] Seeking status of the Streams API spec
Hi Arthur,
OK
On 10/14/14 11:06 PM, Takeshi Yoshino wrote:
Not to confuse people, too late but I replaced the W3C Streams API
spec WD with a pointer to the WHATWG Streams spec and a few sections
discussing what we should add to the spec for browser use cases.
Takeshi - given the magnitude of the changes in
: [streams-api] Seeking status of the Streams API spec
Re: establishing integration plan for the consumers and producers listed in the
W3C spec, we haven't done anything than what Domenic introduced in this thread.
I wrote some draft of XHR+ReadableStream integration spec and is implemented
From: Paul Cotton [mailto:paul.cot...@microsoft.com]
Would it be feasible to resurrect this interface as a layer on top of [1] so
that W3C specifications like MSE that have a dependency on the Streams
interface are not broken?
The decision we came to in web apps some months ago was that
Yoshino
Cc: Jerry Smith (WINDOWS); Anne van Kesteren; public-webapps; Arthur Barstow;
Feras Moussa; public-html-me...@w3.org; Aaron Colwell
Subject: RE: [streams-api] Seeking status of the Streams API spec
From: Paul Cotton [mailto:paul.cot...@microsoft.com]
Would it be feasible to resurrect
On Wed, Oct 15, 2014 at 11:24 AM, Domenic Denicola
dome...@domenicdenicola.com wrote:
From: Paul Cotton [mailto:paul.cot...@microsoft.com]
Would it be feasible to resurrect this interface as a layer on top of
[1] so that W3C specifications like MSE that have a dependency on the
Streams
On Mon, Oct 13, 2014 at 10:00 PM, Paul Cotton paul.cot...@microsoft.com wrote:
MSE is in CR and there are shipping implementations.
Yes, but the Stream object is not shipping. Unless Microsoft has a
prototype it is in exactly 0 implementations. So MSE would have to get
out of CR anyway to get
From: annevankeste...@gmail.com [mailto:annevankeste...@gmail.com] On Behalf Of
Anne van Kesteren
On Mon, Oct 13, 2014 at 10:00 PM, Paul Cotton paul.cot...@microsoft.com
wrote:
MSE is in CR and there are shipping implementations.
Yes, but the Stream object is not shipping. Unless Microsoft
From: Domenic Denicola [mailto:dome...@domenicdenicola.com]
The more interesting question is whether BufferSource is shipping
(unprefixed), since ideally we would make BufferSource a WritableStream.
Sorry, SourceBuffer, not BufferSource---both in this message and the previous
one.
Yes SourceBuffer is shipping and has been for quite some time in Chrome and
IE. Firefox and Safari have been working on implementations for quite some
time as well. I am NOT going to rework it all to be a WritableStream. I am
just looking to adjust appendStream() to take whatever object replaced
From: Aaron Colwell [mailto:acolw...@google.com]
Yes SourceBuffer is shipping and has been for quite some time in Chrome and
IE.
Hmm, window.SourceBuffer is undefined in Chrome.
I am NOT going to rework it all to be a WritableStream.
That's a shame, but completely understandable that you
On Tue, Oct 14, 2014 at 9:19 AM, Domenic Denicola
dome...@domenicdenicola.com wrote:
From: Aaron Colwell [mailto:acolw...@google.com]
Yes SourceBuffer is shipping and has been for quite some time in Chrome
and IE.
Hmm, window.SourceBuffer is undefined in Chrome.
You can only create
From: Aaron Colwell [mailto:acolw...@google.com]
MSE is just too far along, has already gone through a fair amount of churn,
and has major customers like YouTube and Netflix that I just don't want to
break or force to migrate...again.
Totally understandable.
I haven't spent much time
-webapps; Arthur
Barstow; Feras Moussa; public-html-me...@w3.org
Subject: RE: [streams-api] Seeking status of the Streams API spec
Where is the latest Streams spec?
https://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm doesn't have much
about WritableStreams.
Jerry
-Original Message
; Takeshi Yoshino; public-webapps;
Arthur Barstow; Feras Moussa; public-html-me...@w3.org
Subject: RE: [streams-api] Seeking status of the Streams API spec
Where is the latest Streams spec?
https://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm doesn't have
much about WritableStreams
To: Domenic Denicola
Cc: public-webapps; Arthur Barstow; Takeshi Yoshino; Feras Moussa
Subject: RE: [streams-api] Seeking status of the Streams API spec
The previous W3C WD [1] identified a large number of specifications that were
stream producers and consumers. Is there any kind of mapping
Denicola [mailto:dome...@domenicdenicola.com]
Sent: Monday, October 13, 2014 2:40 PM
To: Paul Cotton
Cc: public-webapps; Arthur Barstow; Takeshi Yoshino; Feras Moussa
Subject: RE: [streams-api] Seeking status of the Streams API spec
Good question. Takeshi should weigh in on this too since he has
From: Paul Cotton [mailto:paul.cot...@microsoft.com]
MSE [1] simply used the Stream object directly from the previous W3C WD
[2]. Since this object no longer is available in [3], what you do recommend
that MSE should do?
OK, down to the fun stuff :). Here's my take based on some brief
From: Domenic Denicola
Sent: 13/10/2014 3:04 PM
To: Paul Cotton; Takeshi Yoshino
Cc: public-webapps; Arthur Barstow; Feras Moussa
Subject: RE: [streams-api] Seeking status of the Streams API spec
From: Paul Cotton [mailto:paul.cot...@microsoft.com]
MSE [1] simply
, August 20, 2014 11:57 PM
To: Arthur Barstow; Takeshi Yoshino; Feras Moussa
Cc: public-webapps; team-html-cha...@w3.org
Subject: RE: [streams-api] Seeking status of the Streams API spec
Hi HTML WG,
The streams API is progressing quite nicely, and is *very* close to being
settled. At this point
From: Paul Cotton [mailto:paul.cot...@microsoft.com]
Was this Aug goal achieved?
Yes: https://streams.spec.whatwg.org/
[mailto:dome...@domenicdenicola.com]
Sent: Thursday, October 09, 2014 4:24 PM
To: Paul Cotton
Cc: public-webapps; Arthur Barstow; Takeshi Yoshino; Feras Moussa
Subject: RE: [streams-api] Seeking status of the Streams API spec
From: Paul Cotton [mailto:paul.cot...@microsoft.com]
Was this Aug goal
, August 18, 2014 14:28
To: Takeshi Yoshino; Feras Moussa; Domenic Denicola
Cc: public-webapps; team-html-cha...@w3.org
Subject: [streams-api] Seeking status of the Streams API spec
Hi All,
The HTML WG would like to know the status of the Streams API and if the
February plan from Feras (see below
Hi All,
The HTML WG would like to know the status of the Streams API and if the
February plan from Feras (see below) is still the plan-of-action. Please
provide an update.
Paul - the last status I saw was the following e-mail from Domenic on
June 27
29 matches
Mail list logo
