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
The Streams API spec has significant changes since its last TR
publication (November 2013). As such, this is an announcement of an
intent to publish a new WD on October 23, using the latest ED as the basis:
https://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm
If anyone has any major
On Tue, Oct 21, 2014 at 3:58 PM, Arthur Barstow art.bars...@gmail.com wrote:
The Streams API spec has significant changes since its last TR publication
(November 2013). As such, this is an announcement of an intent to publish a
new WD on October 23, using the latest ED as the basis:
On 21 Oct 2014 16:53, Shijun Sun shij...@microsoft.com wrote:
On Monday, October 20, 2014 9:42 AM, Jake Archibald wrote:
Things I guess you'd do as a result of a push message:
One of the most typical scenarios is
* show a toast notification (e.g. for a new email)
* user chooses to dismiss
Folks,
I'm looking for help to a couple more questions on the Push API.
1. What is the typical lifetime expected for a PushRegistration?
2. IF a PushRegistration can expire, what would be the right option(s) to
renew the push service?
All the Best, Shijun
Hello,
I'm with the IE Platform team at Microsoft. We have a few comments on the
latest editor's draft of the newly proposed FileSystem API [1].
1.1 Use cases (3. Audio/Photo editor with offline access or local cache for
speed)
* Edited files should be accessible by other client-side
On 10/21/14 4:36 PM, Ali Alabbas wrote:
Hello,
I'm with the IE Platform team at Microsoft. We have a few comments on
the latest editor's draft of the newly proposed FileSystem API [1].
I believe [1] is Arun's http://w3c.github.io/filesystem-api/Overview.html.
1.1 Use cases (3.
On 10/16/14 5:52 PM, Shijun Sun wrote:
On Thursday, October 16, 2014 11:46 AM, Martin Thomson wrote
If the push message is being used to deliver a call notification, that sort of
delay will definitely be noticed. And I'm assuming that you've tested on a
high end Nexus or something like that.
On Tuesday, October 21, 2014 2:27 PM, Arthur Barstow wrote:
If we want to take advantage of this opportunity, perhaps you
should first flesh out specific issue(s) to discuss, and then try to agree on
a time
+ day slot in advance of the meeting.
Thanks Arthur for the suggestion.
I think
