On 10/7/11 8:32 AM, ext Julian Reschke wrote:
As far as I recall, we agreed in the IETF WG that parsing of web
socket URIs should work exactly the same way as for any other URI
scheme. It appears that the API spec now tries to override this, and
this looks problematic to me.
On 10/7/11 9:30
This is a Call for Consensus to publish a WD of Server-Sent Events (last
published 10-Mar-2011):
http://dev.w3.org/html5/eventsource/
Positive response to this CfC is preferred and encouraged and silence
will be considered as agreement with the proposal. The deadline for
comments is
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14412
Summary: IDBFactorySync should have .cmp too
Product: WebAppsWG
Version: unspecified
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: normal
Priority: P2
Hello,
http://www.w3.org/TR/file-system-api/#the-flags-interface
If you look at the description of exclusive flag (4.2.1), the
description states no exception, but the example (4.2.2) uses
exception to determine whether file already existed.
So the question is, what is wrong: the description
The exception is thrown by getFile on DirectoryEntrySync, not by the
Flags constructor; both the example and the flags interface are
correct.
On Sat, Oct 8, 2011 at 11:54 AM, Bronislav Klučka
bronislav.klu...@bauglir.com wrote:
Hello,
http://www.w3.org/TR/file-system-api/#the-flags-interface
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14414
Summary: Is it really can be used like Winsocket? How can I use
it?
Product: WebAppsWG
Version: unspecified
Platform: Other
URL:
