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)
Howdy.
interface StorageInfo {
Should probably be QuotaInfo or even QuotaManager ? Storage can and
will be confused with Web Storage.
// storage type
const unsigned short TEMPORARY = 0;
const unsigned short PERSISTENT = 1;
Only two values seem not enough for me and I disagre
On Thu, 25 Nov 2010 14:27:57 +0100, Anne van Kesteren ann...@opera.com
wrote:
On Wed, 24 Nov 2010 19:54:15 +0100, Eric Uhrhane er...@google.com
wrote:
In the XHR2 spec, most references to progress events make it clear
that they're only sent for asynchronous XHRs. However, in three
cases, the
On Sat, 29 Jan 2011 08:41:55 +0100, David Flanagan
da...@davidflanagan.com wrote:
I just noticed this in the XHR2 spec:
If data is a Blob
If the object is of type File and its mediaType attribute is not
the empty string let mime type be its value.
I think this must reference an
Anne, others,
Do you have any opinions on this?
There have recently been some good discussions around HTTP
authentication on IETF mailing lists, and I think having some
flexibility here would be useful in the long run.
tim
On Thu, Jan 06, 2011 at 08:50:00AM -0800, Tim wrote:
Hello,
It
On Thu, Feb 3, 2011 at 4:32 AM, João Eiras joao.ei...@gmail.com wrote:
Howdy.
interface StorageInfo {
Should probably be QuotaInfo or even QuotaManager ? Storage can and
will be confused with Web Storage.
// storage type
const unsigned short TEMPORARY = 0;
const unsigned
Should probably be QuotaInfo or even QuotaManager ? Storage can and
will be confused with Web Storage.
// storage type
const unsigned short TEMPORARY = 0;
const unsigned short PERSISTENT = 1;
Only two values seem not enough for me and I disagre with the
nomenclature. Would be
together with other forms
of authentication, and that moving to TLS Extension support would
probably be wise in the long term.
see: http://krijnhoetmer.nl/irc-logs/whatwg/20110203#l-870
through to 14:51 for context
Thanks for raising this,
Nathan
Tim wrote:
Anne, others,
Do you have any
On Feb/1/2011 1:30 PM, ext Marcos Caceres wrote:
I have updated the Wigets PC spec for publication as a LC.
This new draft specifies the defaultlocale attribute
Is support for this proposed attribute going to be added to the Widget
object? (I don't see it mentioned in latest ED of the Widget
On 2/3/11 8:08 PM, Arthur Barstow wrote:
On Feb/1/2011 1:30 PM, ext Marcos Caceres wrote:
I have updated the Wigets PC spec for publication as a LC.
This new draft specifies the defaultlocale attribute
Is support for this proposed attribute going to be added to the Widget
object? (I don't
On Thu, Feb 3, 2011 at 9:23 AM, João Eiras joao.ei...@gmail.com wrote:
Should probably be QuotaInfo or even QuotaManager ? Storage can and
will be confused with Web Storage.
// storage type
const unsigned short TEMPORARY = 0;
const unsigned short PERSISTENT = 1;
Only two values
On Thu, Feb 3, 2011 at 2:25 AM, Kinuko Yasuda kin...@chromium.org wrote:
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
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11976
Summary: Autoincrement keys need to be cleaned up some in the
spec
Product: WebAppsWG
Version: unspecified
Platform: PC
OS/Version: All
Status: NEW
On Thu, Feb 3, 2011 at 5:25 AM, Kinuko Yasuda kin...@chromium.org wrote:
interface StorageInfo {
// storage type
const unsigned short TEMPORARY = 0;
const unsigned short PERSISTENT = 1;
// To query how much storage is available and currently in use.
void
It shouldn't fire both error and abort. We're fixing this :)
- Original Message -
Hi
http://dev.w3.org/2006/webapi/FileAPI/#abort
Why does it fire both error and abort? Shouldn't it just fire abort?
--
Simon Pieters
Opera Software
Before storing X amount of data with an API, the code requests enough
space for the storage area that API covers. That's how I understand
the use case. Then it's up to the user agent to communicate that
appropriately to the user, if applicable.
Why would we need to have the app specify I want
On 2/3/2011 3:59 PM, João Eiras wrote:
Because the user agent needs to differentiate which api will use each
quota.
But why does a user agent need to do that? It seems like that is adding
unnecessary complication to the API.
Cheers,
Shawn
smime.p7s
Description: S/MIME Cryptographic
On Thu, Feb 3, 2011 at 3:59 PM, João Eiras joao.ei...@gmail.com wrote:
Before storing X amount of data with an API, the code requests enough
space for the storage area that API covers. That's how I understand
the use case. Then it's up to the user agent to communicate that
appropriately to
On , Shawn Wilsher sdwi...@mozilla.com wrote:
On 2/3/2011 3:59 PM, João Eiras wrote:
Because the user agent needs to differentiate which api will use each
quota.
But why does a user agent need to do that? It seems like that is adding
unnecessary complication to the API.
Or adding
On 2/3/2011 4:35 PM, João Eiras wrote:
Or adding unnecessary complication to the implementation.
I'm not looking to make my job easier (as an implementer); I'm looking
to make it easy to use. At least with IndexedDB, we generally choose
the option that is easier for the consumer as long as it
I rather like the prompt in the new FF builds; it's similar to the
prompt on Mobile Safari;
when you get into the site, it asks you if you're ok storing data, and
it allows you to specify a quota stepping.
FF does a great job on applicationCache + quota in that area.
The FileSystem API is a
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11978
Summary: Section: Abstract Problem: this specification defines
two mecahism for... should read mechanisms.
Product: WebAppsWG
Version: unspecified
Platform: Other
URL:
On Tue, Feb 1, 2011 at 11:00 AM, bugzi...@jessica.w3.org wrote:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11948
Summary: index.openCursor's cursor should have a way to access
the index's value (in addition to the index's key
and
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
I'm not sure FileSystem is necessarily any trickier from a user's
perspective -- it's all storage that is taking up space on my HD (at least,
for now the filesystem is just a directory under the user's profile in
Chrome). I think it fits fine in the unified quota model. (And FWIW we are
looking at
On 2/3/2011 9:39 PM, Ian Fette (イアンフェッティ) wrote:
I'm not sure FileSystem is necessarily any trickier from a user's
perspective -- it's all storage that is taking up space on my HD (at
least, for now the filesystem is just a directory under the user's
profile in Chrome). I think it fits fine in
On Thu, Feb 3, 2011 at 10:07 PM, Charles Pritchard ch...@visc.us wrote:
On 2/3/2011 9:39 PM, Ian Fette (イアンフェッティ) wrote:
I'm not sure FileSystem is necessarily any trickier from a user's
perspective -- it's all storage that is taking up space on my HD (at least,
for now the filesystem is
On 2/3/2011 10:36 PM, Ian Fette (イアンフェッティ) wrote:
On Thu, Feb 3, 2011 at 10:07 PM, Charles Pritchard ch...@visc.us
mailto:ch...@visc.us wrote:
On 2/3/2011 9:39 PM, Ian Fette (イアンフェッティ) wrote:
I'm not sure FileSystem is necessarily any trickier from a
user's perspective --
28 matches
Mail list logo
