Hi,
(After some pause) I've updated the spec to include the event loop
description for handling asynchronous callbacks:
https://dvcs.w3.org/hg/quota/raw-file/tip/Overview.html
https://dvcs.w3.org/hg/quota/raw-file/tip/Overview.html#methods
I basically followed other specs and the wiki page
On Wed, Jun 27, 2012 at 8:18 AM, Kinuko Yasuda kin...@chromium.org wrote:
(After some pause) I've updated the spec to include the event loop
description for handling asynchronous callbacks:
https://dvcs.w3.org/hg/quota/raw-file/tip/Overview.html
On Wed, Jun 27, 2012 at 10:44 PM, Glenn Maynard gl...@zewt.org wrote:
On Wed, Jun 27, 2012 at 8:18 AM, Kinuko Yasuda kin...@chromium.orgwrote:
(After some pause) I've updated the spec to include the event loop
description for handling asynchronous callbacks:
On 06/27/2012 05:44 PM, Tobie Langel wrote:
On Jun 27, 2012, at 6:44 AM, Glenn Maynardgl...@zewt.org wrote:
Unrelated, screaming-caps on RFC2119 terms (eg. MUST) is jarring
and unnecessary. I'd suggest dropping the em.rfc2119 style.
That's what HTML, DOM4, etc. do, and it's much more
On Wed, Jun 27, 2012 at 8:44 AM, Tobie Langel to...@fb.com wrote:
On Jun 27, 2012, at 6:44 AM, Glenn Maynard gl...@zewt.org wrote:
Unrelated, screaming-caps on RFC2119 terms (eg. MUST) is jarring and
unnecessary. I'd suggest dropping the em.rfc2119 style. That's what HTML,
DOM4, etc. do,
On Jun 27, 2012, at 9:14, Ms2ger ms2...@gmail.com wrote:
On 06/27/2012 05:44 PM, Tobie Langel wrote:
On Jun 27, 2012, at 6:44 AM, Glenn Maynardgl...@zewt.org wrote:
Unrelated, screaming-caps on RFC2119 terms (eg. MUST) is jarring
and unnecessary. I'd suggest dropping the em.rfc2119 style.
Based on the feedbacks I've updated the draft:
http://dvcs.w3.org/hg/quota/raw-file/tip/Overview.html
- Got rid of string enum, instead introduced navigator.persistentStorage
and navigator.temporaryStorage
- Some interface name changes (just for IDL)
QuotaStorageEnvironment -
On Wed, Jun 6, 2012 at 8:33 AM, Kinuko Yasuda kin...@chromium.org wrote:
http://dvcs.w3.org/hg/quota/raw-file/tip/Overview.html
I noticed something unrelated to the naming. Because you define
asynchronous callbacks, you need to define the methods in terms of the
HTML event loop. Otherwise it is
On Wed, Jun 6, 2012 at 4:27 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Wed, Jun 6, 2012 at 8:33 AM, Kinuko Yasuda kin...@chromium.org wrote:
http://dvcs.w3.org/hg/quota/raw-file/tip/Overview.html
I noticed something unrelated to the naming. Because you define
asynchronous callbacks,
On 6/6/12 8:33 AM, Kinuko Yasuda kin...@chromium.org wrote:
Based on the feedbacks I've updated the draft:
http://dvcs.w3.org/hg/quota/raw-file/tip/Overview.html
- Got rid of string enum, instead introduced navigator.persistentStorage
and navigator.temporaryStorage
- Some interface name changes
On Mon, Jun 4, 2012 at 6:30 PM, Tobie Langel to...@fb.com wrote:
On 6/4/12 11:17 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Mon, Jun 4, 2012 at 11:01 AM, Tobie Langel to...@fb.com wrote:
Finally, I feel it's slightly misleading to have an interface called
info which enables changes
On 6/1/12 12:07 PM, Kinuko Yasuda kin...@chromium.org wrote:
Makes sense, ok let's keep it. Then we will have symmetric four
methods, request and query for each type.
Following up on the conversation on Quota Management API and the recent
changes which were agreed upon, I'm wondering whether we
On Mon, Jun 4, 2012 at 11:01 AM, Tobie Langel to...@fb.com wrote:
Finally, I feel it's slightly misleading to have an interface called
info which enables changes (through `requestQuota`). Wouldn't settings
or similar be more appropriate? As in:
On 6/4/12 11:17 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Mon, Jun 4, 2012 at 11:01 AM, Tobie Langel to...@fb.com wrote:
Finally, I feel it's slightly misleading to have an interface called
info which enables changes (through `requestQuota`). Wouldn't
settings
or similar be more
On Thu, May 31, 2012 at 4:50 AM, Tobie Langel to...@fb.com wrote:
On 5/30/12 9:03 PM, Eric U er...@google.com wrote:
On Wed, May 30, 2012 at 11:59 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 5/30/12 2:05 PM, Eric Uhrhane wrote:
How about session, which is guaranteed to go away when the
On 6/1/12 10:34 AM, Kinuko Yasuda kin...@chromium.org wrote:
If we go along the line we will have four methods on StorageInfo:
queryPersistentUsageAndQuota
queryTemporaryUsageAndQuota
requestPersistentQuota
We could also think of 'requestTemporaryQuota', a variant of
requestQuota, but by the
Makes sense, ok let's keep it. Then we will have symmetric four methods,
request and query for each type.
On Jun 1, 2012 6:17 PM, Tobie Langel to...@fb.com wrote:
On 6/1/12 10:34 AM, Kinuko Yasuda kin...@chromium.org wrote:
If we go along the line we will have four methods on StorageInfo:
Thanks for the feedback!
On Tue, May 29, 2012 at 11:07 PM, Tobie Langel to...@fb.com wrote:
On 5/17/12 11:02 AM, Kinuko Yasuda kin...@chromium.org wrote:
For context for others, I assume they are comments for the draft pushed
at:
https://dvcs.w3.org/hg/quota/Overview.html
I'm super
On 5/30/12 6:30 PM, Kinuko Yasuda kin...@chromium.org wrote:
Thanks for the feedback!
On Tue, May 29, 2012 at 11:07 PM, Tobie Langel to...@fb.com wrote:
On 5/17/12 11:02 AM, Kinuko Yasuda kin...@chromium.org wrote:
For context for others, I assume they are comments for the draft pushed
at:
On Wed, May 30, 2012 at 9:54 AM, Tobie Langel to...@fb.com wrote:
On 5/30/12 6:30 PM, Kinuko Yasuda kin...@chromium.org wrote:
Thanks for the feedback!
On Tue, May 29, 2012 at 11:07 PM, Tobie Langel to...@fb.com wrote:
On 5/17/12 11:02 AM, Kinuko Yasuda kin...@chromium.org wrote:
For
On 5/30/12 2:05 PM, Eric Uhrhane wrote:
How about session, which is guaranteed to go away when the browser
exits
Should it go away if the browser crashes (or is killed by an OOM killer
or the background process killer on something like Android) and then
restarts and restores the session?
On Wed, May 30, 2012 at 11:59 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 5/30/12 2:05 PM, Eric Uhrhane wrote:
How about session, which is guaranteed to go away when the browser
exits
Should it go away if the browser crashes (or is killed by an OOM killer or
the background process killer
On 5/30/12 9:03 PM, Eric U er...@google.com wrote:
On Wed, May 30, 2012 at 11:59 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 5/30/12 2:05 PM, Eric Uhrhane wrote:
How about session, which is guaranteed to go away when the browser
exits
Should it go away if the browser crashes (or is killed
On 5/17/12 11:02 AM, Kinuko Yasuda kin...@chromium.org wrote:
Thanks for the feedback!
For context for others, I assume they are comments for the draft pushed
at:
https://dvcs.w3.org/hg/quota/Overview.html
I'm super excited to see an API for this is in the works. It's been a much
wanted
On Wed, May 23, 2012 at 9:32 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Wed, May 23, 2012 at 2:05 PM, Kinuko Yasuda kin...@chromium.org
wrote:
https://dvcs.w3.org/hg/quota/raw-file/tip/Overview.html
I noticed something else. StorageInfo is marked as Supplemental and
On Wed, May 23, 2012 at 2:05 PM, Kinuko Yasuda kin...@chromium.org wrote:
https://dvcs.w3.org/hg/quota/raw-file/tip/Overview.html
I noticed something else. StorageInfo is marked as Supplemental and
NoInterfaceObject, but I do not think either is meant to be used here.
Supplemental has been
On Tue, May 22, 2012 at 2:46 AM, Eric Uhrhane er...@chromium.org wrote:
On Thu, May 17, 2012 at 2:02 AM, Kinuko Yasuda kin...@chromium.org
wrote:
Thanks for the feedback!
For context for others, I assume they are comments for the draft pushed
at:
On Tue, May 22, 2012 at 11:21 AM, Kinuko Yasuda kin...@chromium.org wrote:
I've updated the draft to use the callback IDL syntax.
You should update the section titles as well. #nit
--
Anne — Opera Software
http://annevankesteren.nl/
http://www.opera.com/
On Tue, May 22, 2012 at 6:45 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, May 22, 2012 at 11:21 AM, Kinuko Yasuda kin...@chromium.org
wrote:
I've updated the draft to use the callback IDL syntax.
You should update the section titles as well. #nit
Yup, thanks, updated the section
On Tue, May 22, 2012 at 4:02 PM, Kinuko Yasuda kin...@chromium.org wrote:
Yup, thanks, updated the section titles together with other changes:
- putting storageInfo on window.navigator rather than on window
- changing TEMPORARY / PERSISTENT constants to a string enum
On Thu, May 17, 2012 at 2:02 AM, Kinuko Yasuda kin...@chromium.org wrote:
Thanks for the feedback!
For context for others, I assume they are comments for the draft pushed at:
https://dvcs.w3.org/hg/quota/Overview.html
On Tue, May 15, 2012 at 8:17 PM, Anne van Kesteren ann...@annevk.nl wrote:
Thanks for the feedback!
For context for others, I assume they are comments for the draft pushed at:
https://dvcs.w3.org/hg/quota/Overview.html
On Tue, May 15, 2012 at 8:17 PM, Anne van Kesteren ann...@annevk.nl wrote:
1) Put storageInfo on window.navigator, not window directly.
That sounds
1) Put storageInfo on window.navigator, not window directly.
2) Use the IDL callback syntax. The current IDL is outdated.
3) Use a string enum rather than a constant.
--
Anne — Opera Software
http://annevankesteren.nl/
http://www.opera.com/
33 matches
Mail list logo
