Sorry for slow response,
On Wed, Apr 2, 2014 at 8:05 PM, Arthur Barstow art.bars...@nokia.comwrote:
Hi All,
The people in the To: list are spec Editors that are not registered for
WebApps' April 10-11 meeting. Since you _won't_ attend the meeting, I would
appreciate it if you would please
Hi Domenic,
On Thu, Mar 27, 2014 at 2:07 PM, Domenic Denicola
dome...@domenicdenicola.com wrote:
Hi everyone,
The TAG recently spent some time looking at the current Quota API draft at
[1], based on some early discussions between Alex and Kinuko. We believe
that the topic of quotas and
On Wed, Dec 11, 2013 at 10:42 PM, Arthur Barstow art.bars...@nokia.comwrote:
On 12/11/13 6:39 AM, ext Simon Pieters wrote:
On Tue, 10 Dec 2013 22:09:38 +0100, Jonas Sicking jo...@sicking.cc
wrote:
We at Mozilla just finished our implementation of Shared Workers. It
will be turned on in
Hi,
I'm glad to hear that IDB's going to support storage types!
On Thu, Dec 12, 2013 at 12:39 PM, Jonas Sicking jo...@sicking.cc wrote:
Hi All,
Thanks Jan for sending this.
Now let me throw a giant wrench into this discussion :-)
Unfortunately as we've been discussing webapps,
On Tue, Oct 29, 2013 at 9:01 PM, Arthur Barstow art.bars...@nokia.comwrote:
Kinuko has made substantive changes [1] to the Quota Management API since
the FPWD was published. As such, this is a Call for Consensus to publish a
new Working Draft using the ED as the basis:
On Thu, Oct 3, 2013 at 11:13 PM, Arthur Barstow art.bars...@nokia.comwrote:
On 10/2/13 9:37 PM, ext Kinuko Yasuda wrote:
I'm planning to update the FPWD to use some new syntax like Promises, and
Mozilla is showing agreement and interest to implement the new draft per
discussion on public
Hi Arthur,
On Thu, Oct 3, 2013 at 1:30 AM, Arthur Barstow art.bars...@nokia.comwrote:
Hi Kinuko,
If any of the data for the Quota Management API spec in [PubStatus] is not
accurate, please provide corrections.
Also, if you have any new information re your plans for the spec - last
On Sat, Aug 24, 2013 at 3:45 PM, Jonas Sicking jo...@sicking.cc wrote:
On Aug 23, 2013 12:30 AM, Kinuko Yasuda kin...@chromium.org wrote:
On Tue, Aug 20, 2013 at 1:49 AM, Jonas Sicking jo...@sicking.cc wrote:
On Mon, Aug 19, 2013 at 9:32 AM, Kinuko Yasuda kin...@chromium.org
wrote
On Tue, Aug 27, 2013 at 4:26 AM, Jonas Sicking jo...@sicking.cc wrote:
Thanks, that explains the concern.
However the proposed solution doesn't seem to solve the problem
particularly well, for two reasons:
First off, an API which lets the website track how much data it is
storing, measured
On Tue, Aug 20, 2013 at 1:49 AM, Jonas Sicking jo...@sicking.cc wrote:
On Mon, Aug 19, 2013 at 9:32 AM, Kinuko Yasuda kin...@chromium.org
wrote:
Actually, *only* having onstoragechange would solve both the use case
of detecting when you are running low on storage, as well as when you
On Sat, Aug 17, 2013 at 3:01 AM, Jonas Sicking jo...@sicking.cc wrote:
On Fri, Aug 16, 2013 at 6:56 AM, Kinuko Yasuda kin...@chromium.org
wrote:
I had a few bike-sheddy comments as well.
Now the new draft looks like:
enum StorageType { temporary, persistent };
partial interface
On Fri, Aug 16, 2013 at 3:25 AM, Jonas Sicking jo...@sicking.cc wrote:
On Thu, Aug 15, 2013 at 9:44 AM, Kinuko Yasuda kin...@chromium.org
wrote:
requestQuota for temporary storage:
I'd like to better understand the use case for requestQuota for
temporary
storage. Are implementations
Hi Joshua,
On Thu, Aug 15, 2013 at 6:33 AM, Joshua Bell jsb...@chromium.org wrote:
PromiseStorageType getStorageType((IDBObjectStore or Database or
Entry) object);
Promisevoid setStorageType((IDBObjectStore or Database or Entry)
object, StorageType type);
For IndexedDB, an object
a storage type just confuses
readers/implementors, we should probably just drop the storage type
parameter and rename it to something like 'requestPersistentQuota', or only
add the method to 'navigator.persistentStorage' attribute?
/ Jonas
On Tue, Aug 13, 2013 at 10:57 PM, Kinuko Yasuda kin
Hi all,
It's been a while since Quota API's FPWD (http://www.w3.org/TR/quota-api/)
was published and we've gotten several requests/feedbacks so far.
To address some of the requests and to gain more consensus, I'm thinking
about making following changes to the Quota API:
* Use Promises rather
On Tue, Jul 23, 2013 at 4:48 AM, Jonas Sicking jo...@sicking.cc wrote:
On Mon, Jul 22, 2013 at 11:18 AM, Jan Varga jan.va...@gmail.com wrote:
On Sat, Jul 13, 2013 at 2:31 AM, Jonas Sicking jo...@sicking.cc wrote:
Hi All,
Yesterday a few of us at mozilla went through the FileSystem API
Glad to see this proposal has a new draft.
On Sat, Jul 13, 2013 at 9:31 AM, Jonas Sicking jo...@sicking.cc wrote:
Executive Summary (aka TL;DR):
Below is the mozilla proposal for a simplified filesystem API. It
contains two new abstractions, a Directory object which allows
manipulating files
On Tue, Jul 16, 2013 at 11:29 AM, Mounir Lamouri mou...@lamouri.fr wrote:
Hi,
I am not a big fan of the Directory approach of this proposal. It puts
the API between a high level, object oriented API and a low level API.
It is unfortunately not really high level because you have to use the
12, 2012 at 12:07 AM, Tobie Langel to...@fb.com wrote:
On 9/11/12 4:06 PM, Charles McCathie Nevile cha...@yandex-team.ru
wrote:
On Tue, 11 Sep 2012 06:29:07 -0400, Kinuko Yasuda kin...@chromium.org
wrote:
On Tue, Sep 11, 2012 at 6:43 PM, Tobie Langel to...@fb.com wrote:
On 9/11/12 11:13
, Tobie Langel to...@fb.com wrote:
On 9/11/12 10:57 AM, Kinuko Yasuda kin...@chromium.org wrote:
Hi Tobie,
Session storage type or some storage options which can be explicitly
'expired' sounds useful.
Through some offline local discussion I've been thinking that having some
configurable 'expire
On Sat, Sep 22, 2012 at 8:32 AM, Eric U er...@google.com wrote:
While I don't see any other browsers showing interest in implementing
the FileSystem API as currently specced,
Just for the record, Blackberry, Tizen/EFL and Netfront seem to have some
support of FileSystem API.
EFL has also
Hi Tobie,
Session storage type or some storage options which can be explicitly
'expired' sounds useful.
Through some offline local discussion I've been thinking that having some
configurable 'expire' option in Temporary or in a new storage type might be
useful in various situations.
On Mon, Sep
Hi,
Thanks for giving the continuous feedback to Quota API.
On Mon, Sep 10, 2012 at 7:46 PM, Tobie Langel to...@fb.com wrote:
Hi,
I'm very happy with the API changes we where able to make to the Quota
API, but there's a method name we have left untouched and that I haven't
figured out how
On Tue, Sep 11, 2012 at 6:43 PM, Tobie Langel to...@fb.com wrote:
On 9/11/12 11:13 AM, Kinuko Yasuda kin...@chromium.org wrote:
I think I like this idea, but I'm also concerned with the fact that
Chromium has been shipping Quota API some time now and there're some
consumers of the old API
(Replying to a message I got separately)
Thanks for the feedback!
Hmm if a write fails because the UA does not grant any quota for the site I
think it must throw a QuotaExceeded exception, so that website authors or
the users could tell how they can re-enable writing to the storage (e.g. by
description you
suggested.
Thanks for your feedbacks,
Kinuko
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
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:
https://dvcs.w3.org/hg/quota/raw
- StorageQuotaEnvironment
StorageInfo - StorageQuota
StorageInfoQuotaCallback - StorageQuotaCallback
StorageInfoUsageCallback - StorageUsageCallback
StorageInfoErrorCallback - StorageErrorCallback
I'd like to finalize these naming/interface details while we're here.
On Tue, Jun 5, 2012 at 10:03 PM, Kinuko
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 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 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
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 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
NoInterfaceObject
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
On Wed, May 23, 2012 at 12:48 AM, Glenn Maynard gl...@zewt.org wrote:
On Tue, May 22, 2012 at 1:41 AM, Kinuko Yasuda kin...@google.com wrote:
In my understanding WebKit's behavior is querying the metadata / reading
the content as lazy as possible, partly because the spec was/is ambiguous
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:
https://dvcs.w3.org/hg/quota
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
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
Hi,
While looking at the FileSystem API draft I noticed that we only expose
'modificationTime' in 'Metadata' object. Since FileEntry itself doesn't
have 'size' field unlike File object maybe it's reasonable to add 'size'
field to Metadata?
Hi,
(Sorry for my slow response, I'm in a half-vacation status)
On Sun, Dec 18, 2011 at 12:19 AM, Charles McCathieNevile
cha...@opera.comwrote:
On Fri, 16 Dec 2011 10:10:45 +0100, Kinuko Yasuda kin...@chromium.org
wrote:
On Thu, Dec 15, 2011 at 9:19 PM, Arthur Barstow art.bars...@nokia.com
/wiki/CharterChanges
Original Message
Subject: Re: Quota API and WebApps [Was: Re: Consolidating charter
changes]
Date: Tue, 13 Dec 2011 17:22:38 +0900
From: ext Kinuko Yasuda kin...@chromium.org
To: Arthur Barstow art.bars...@nokia.com
CC: public
Hi Arthur,
On Wed, Nov 23, 2011 at 10:20 PM, Arthur Barstow art.bars...@nokia.comwrote:
Hi IanF, All,
Following up on Quota API vis-à-visCharterChanges wiki [1] ...
Does the group want to add Quota API to the group's charter? If yes, where
is a draft/strawman proposal?
We have an early
(Sorry for replying to somewhat ancient thread)
On Wed, Sep 28, 2011 at 1:43 AM, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Sep 27, 2011 at 6:12 AM, Kinuko Yasuda kin...@chromium.org
wrote:
Just to confirm: Yes the interfaces are vendor prefixed (WebKit), and
WebSQL, AppCache, IDB
Thanks for all the feedbacks so far.
Now that the thread became quieter, I hope we're getting agreed,
at least on the basic concept. To make the points clearer, let me
summarize what is being proposed (and what is not) with the quota API:
- To have unified, shared quotas between different
Some other topics I have not (explicitly) responded yet:
On Thu, Feb 3, 2011 at 9:32 PM, João Eiras joao.ei...@gmail.com wrote:
interface StorageInfo {
Should probably be QuotaInfo or even QuotaManager ? Storage can and
will be confused with Web Storage.
I have no strong opinion here,
On Sat, Feb 5, 2011 at 7:29 AM, Glenn Maynard gl...@zewt.org wrote:
On Fri, Feb 4, 2011 at 12:07 AM, Kinuko Yasuda kin...@chromium.org wrote:
If we want to make the quota API treat each API differently this would
make a lot sense, but I'm not fully convinced by the idea.
Putting aside
Hi,
Back then there has been a long thread [1] about how/whether we want to
allow web apps to request quotas for IndexedDB, or for any of the offline
storages (i.e. IndexedDB, FileSystem, appCache, localStorage and SQL DB).
In short there were two topics discussed:
1) introducing (at least)
Thanks for all of your feedbacks.
So it seems like one of the main discussion topic is whether we want to
have shared quota between multiple storage mechanisms (per origin,
per persistent/temporary storage class) or not.
On Fri, Feb 4, 2011 at 9:33 AM, Jonas Sicking jo...@sicking.cc wrote:
I
On Fri, Sep 24, 2010 at 1:15 PM, Eric Uhrhane er...@google.com wrote:
The abort sequence in FileWriter looks like this:
If readyState is DONE, throw a FileException with error code
INVALID_STATE_ERR and terminate this overall series of steps.
Set readyState to DONE.
Terminate any steps
On Thu, Sep 16, 2010 at 4:00 PM, Eric Uhrhane er...@google.com wrote:
2010/9/16 Kinuko Yasuda kin...@chromium.org:
On Thu, Sep 16, 2010 at 2:50 PM, Eric Uhrhane er...@google.com wrote:
How about this?
For a move/copy of a file on top of existing file, or a directory on
top of an existing
On Thu, Sep 9, 2010 at 12:12 AM, Kinuko Yasuda kin...@chromium.org wrote:
On Tue, Sep 7, 2010 at 6:12 PM, Eric Uhrhane er...@google.com wrote:
On Mon, Aug 30, 2010 at 9:27 PM, Kinuko Yasuda kin...@chromium.org
wrote:
Hi,
I have a question about Entry.moveTo/copyTo behavior defined
Hi Eric,
(re-sending from the correct address)
I've been re-reading the spec and started wondering if we really want to
have a new interface / javascript object for Flags.
The Flags interface is used to specify two behavioral options (CREATE and
EXCLUSIVE) for DirectoryEntry.getFile and
Hi,
I have a question about Entry.moveTo/copyTo behavior defined in
the File API: Directories and System [1].
Currently the API doesn't specify how Entry.moveTo() and copyTo() should
behave
when a source entry is a file and there's *already* a file at the
destination path.
Should UAs overwrite
response; I'm now back from my vacation.
On Tue, Jul 20, 2010 at 6:27 PM, Kinuko Yasuda kin...@google.com wrote:
Hi Eric,
Thanks for brushing up the draft.
We had some internal discussion about the API details and came up with a
question regarding is{File,Directory} attributes of Entry
On Fri, Aug 13, 2010 at 10:58 AM, Eric Uhrhane er...@google.com wrote:
On Thu, Aug 12, 2010 at 11:08 PM, Kinuko Yasuda kin...@chromium.org
wrote:
Hi Eric,
Thanks for your reply.
Actually after sending that email I had started to think that caching
isFile
/ isDirectory information
Hi Eric,
Thanks for brushing up the draft.
We had some internal discussion about the API details and came up with a
question regarding is{File,Directory} attributes of Entry interface.
It seems like user agent needs to be able to tell if a given entry is file
or directory synchronously (or from
57 matches
Mail list logo
