On Thu, May 24, 2012 at 2:54 AM, Jonas Sicking jo...@sicking.cc wrote:
No change came out of this thread. I think we established that there
is a need for chunked-arraybuffer. This thread contained some
controversy about whether chunked-text is needed, but in the end the
controversy didn't
Thanks to the inestimable help of the W3C staff I am now plugged into the
mercurial mainline and have uploaded the first stab at the Push API
http://dvcs.w3.org/hg/push/raw-file/default/index.html
I incorporated Mozilla's client API ideas in
On 05/24/2012 09:14 AM, SULLIVAN, BRYAN L wrote:
Thanks to the inestimable help of the W3C staff I am now plugged into
the mercurial mainline and have uploaded the first stab at the Push
API
http://dvcs.w3.org/hg/push/raw-file/default/index.html
A couple of notes on the WebIDL:
* PushManager
On May 23, 2012, at 20:40 , Anne van Kesteren wrote:
how does ReSpec.js use or promote the discouraged particulars?
Most specifications (if not all) using ReSpec.js have this problem. I
believe that is because it is the default setup.
Yup, it's just the default setup. As I've said before,
On May 23, 2012, at 20:30 , Anne van Kesteren wrote:
On Wed, May 23, 2012 at 5:55 PM, Dimitri Glazkov dglaz...@chromium.org
wrote:
Should I be concerned about what seems to be a lively competition
between ReSpec and Anolis. Do we need this tussle? Can we not just
decide which tool to use?
On May 23, 2012, at 14:45 , Anne van Kesteren wrote:
I have made some updates to the howto spec wiki page outlining how
you should go about writing a specification, with some emphasis on
specifications for APIs.
http://wiki.whatwg.org/wiki/Howto_spec
In particular the Patterns and Legacy
The current draft URL spec has a number of Parameter-related methods
(getParameterNames, getParameterValues, hasParameter, getParameter,
setParameter, addParameter, removeParameter, clearParameters)[1]. Apparently
these methods refer to key-value pairs in the query part of the URL as
On 2012-05-24 11:29, Maciej Stachowiak wrote:
The current draft URL spec has a number of Parameter-related methods (getParameterNames, getParameterValues,
hasParameter, getParameter, setParameter, addParameter, removeParameter, clearParameters)[1]. Apparently
these methods refer to key-value
There is a list called spec-p...@w3.org which is about things to do with
making specs. I.e. for editors, in particular. I forwarded some stuff from
this thread there - there are other preprocessing systems around,
including XML toolsets. I think this stuff used to be documented
somewhere,
+1 (top post FTW)
cheers
On Thu, 24 May 2012 11:29:24 +0200, Maciej Stachowiak m...@apple.com
wrote:
The current draft URL spec has a number of Parameter-related methods
(getParameterNames, getParameterValues, hasParameter, getParameter,
setParameter, addParameter, removeParameter,
Thanks for the comments. I updated the spec:
- define what happens when url is omitted
- remove [NoInterfaceObject]
- define readyState as a unsigned short (that was what was meant in the first
place)
- fix cut/paste errors
I still have to find the source of resolve a url as that's a function I
Sorry, cut paste error: the spec is at:
http://dvcs.w3.org/hg/push/raw-file/default/index.html
Thanks,
Bryan Sullivan
-Original Message-
From: SULLIVAN, BRYAN L
Sent: Thursday, May 24, 2012 6:02 AM
To: 'Ms2ger'
Cc: public-webapps
Subject: RE: Push API draft uploaded
Thanks for the
Hi Brian,
On 05/24/2012 03:02 PM, SULLIVAN, BRYAN L wrote:
Thanks for the comments. I updated the spec:
- define what happens when url is omitted
- remove [NoInterfaceObject]
- define readyState as a unsigned short (that was what was meant in the first
place)
- fix cut/paste errors
I still
Web applications need a way to communicate between two same domain
tabs without polling LocalStorage and without hitting the disk.
It would be useful to have an in-memory get/set/compare_and_set hash
table exposed to scripts running same domain tabs, that is discarded
by the browser when those
On Thu, May 24, 2012 at 8:42 AM, Joran Greef jo...@ronomon.com wrote:
Web applications need a way to communicate between two same domain
tabs without polling LocalStorage and without hitting the disk.
I think shared Workers can handle most of this.
--
Glenn Maynard
OK, I corrected the [NoInterfaceObject] (I hope), and referenced HTML5 for
resolving a URL.
The numeric readyState was borrowed from EventSource. I will look at the
thread, but I think this is something that I will just align with the consensus
in the group once determined. I don't have a
On 5/24/2012 7:08 AM, SULLIVAN, BRYAN L wrote:
OK, I corrected the [NoInterfaceObject] (I hope), and referenced HTML5 for
resolving a URL.
The numeric readyState was borrowed from EventSource. I will look at the
thread, but I think this is something that I will just align with the consensus
Re a particular type of Push service that it supports this is intended to be
generic so that new services (perhaps identified by unique URI schemes) can be
covered under this.
That being said, WebSockets schemes clearly would imply that protocol, but http
schemes could be more flexible. One of
This is a Request for Comments re the 24-May-2012 LCWD version of the
WebSocket API:
http://www.w3.org/TR/2012/WD-websockets-20120524/
The comment deadline is June 14 and all comments should be sent to the
public-webapps@w3.org list. The Bugzilla component for the API is [Bugz].
I Cc'ed
This is a Request for Comments re the 24-May-2012 LCWD version of
Indexed Database:
http://www.w3.org/TR/2012/WD-IndexedDB-20120524/
The comment deadline is June 21 and all comments should be sent to the
public-webapps@w3.org list.
-Thanks, AB
Hi there,
here's some early feedback.
A control character is a character whose value is less than or equal to
U+0020 ( ).
This is really surprising; it doesn't match Unicode
(http://www.unicode.org/charts/PDF/U.pdf) nor IETF ABNF (RFC 5234).
I think it would be better to exclude
On 2012-05-24 19:20, Arthur Barstow wrote:
This is a Request for Comments re the 24-May-2012 LCWD version of the
WebSocket API:
http://www.w3.org/TR/2012/WD-websockets-20120524/
The comment deadline is June 14 and all comments should be sent to the
public-webapps@w3.org list. The Bugzilla
On Thu, May 24, 2012 at 8:27 AM, Jonas Sicking jo...@sicking.cc wrote:
On Mon, May 21, 2012 at 4:05 PM, Eric U er...@google.com wrote:
According to the latest editor's draft [1], a File object must always
return an accurate lastModifiedDate if at all possible.
On getting, if user agents can
This seems sensible. I've updated the WebKit patch to do exactly this:
https://bugs.webkit.org/show_bug.cgi?id=84646
It appears that the details of the proposal are now sorted out. I'll
start a new thread describing the full API semantics.
On Fri, May 18, 2012 at 8:29 PM, Ryosuke Niwa
24 matches
Mail list logo
