On Thu, Nov 19, 2009 at 2:03 PM, Kai Hendry hen...@aplix.co.jp wrote:
http://git.webconverger.org/?p=faq;a=commit;h=1f335b2997aedb034ca92d06bf815c623939179e
Please forgive the informal prose.
Yeah, like we are soo serious here! :P If it makes you feel
better, I'm responding to your email
On Nov 20, 2009, at 6:53 AM, Barstow Art (Nokia-CIC/Boston) wrote:
This is a Call for Consensus to publish a Last Call Working Draft of
each of the following specs:
1. Server-Sent Events
http://dev.w3.org/html5/eventsource/
2. Web Storage
http://dev.w3.org/html5/webstorage/
3. Web
On Nov 10, 2009, at 12:24 PM, Kris Zyp wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nikunj R. Mehta wrote:
Hi Kris,
Thanks for the insightful feedback.
On Nov 7, 2009, at 8:12 PM, Kris Zyp wrote:
Is there any intended restrictions on caching of objects returned by
queries and
I have a few problems with the WebSocket API as it is described.
If the client is sending too much data to the server, I don't want it
to be disconnected just because some buffer is temporarily full, but
that is the required semantics of the API. If my application must send
out a lot of data, I
This comment on XMLHttpRequest [1] is from the Forms WG.
A standalone W3C Recommendation-track document is welcome, particularly because
of the statement in [2] The goal of this specification is to document a
minimum set of interoperable features based on existing implementations,
allowing Web
On 11/25/09 3:46 PM, Klotz, Leigh wrote:
The XMLHttpRequest functionality described in this document has
previously been well isolated, and in fact XHR itself has beeen
implemented by a number of different desktop browser vendors by
copying the original implementations.
Note that these were
Boris,
Thank you for your response. I appreciate your asking the clarifying
questions. I'll put some answers inline below.
Please consider these answers to be part of the Forms WG comment as well.
Leigh.
-Original Message-
From: Boris Zbarsky [mailto:bzbar...@mit.edu]
Sent:
Please note (for the record) the following reference from public-webapps on
this topic before.
(The lists.w3.org archives seem to be stuck in 2008.)
http://article.gmane.org/gmane.org.w3c.appformats/8012
Leigh.
-Original Message-
From: public-forms-requ...@w3.org
On Nov 24, 2009, at 7:40 PM, Ian Hickson wrote:
On Fri, 20 Nov 2009, Arthur Barstow wrote:
Based on the responses for this call for comments, I see the next
steps as:
1. Server-sent Events, Web Storage and Web Workers - ready for LCWD
publication. Later today I will begin a CfC to
On Thu, Nov 26, 2009 at 3:48 AM, Sebastian Andersson bof...@gmail.comwrote:
If the client is sending too much data to the server, I don't want it
to be disconnected just because some buffer is temporarily full, but
that is the required semantics of the API. If my application must send
out a
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8358
Ian 'Hixie' Hickson i...@hixie.ch changed:
What|Removed |Added
Status|NEW |RESOLVED
On Fri, 12 Oct 2007, Mihai Sucan wrote:
Change the specification, and base all the storage, on a single unified
approach. Let all the storage data be in SQL databases.
Keep the current definition of the client-side database storage API,
which allows developers to use SQL databases, and
On Tue, 30 Jun 2009, João Eiras wrote:
The webstorage specification needs an API to delete a database, because
there's no such way to do it currently.
Something like deleteDatabase(name) would be good. And after calling it, all
open transactions would be marked as invalid.
The user agent
Deleting all the data in the database (i.e. dropping all the tables)
should be sufficient, no? There's nothing to store if you don't have any
data in the database (in particular, there's no reason to store the
version as far as I can tell -- you can just act as if the user deleted
the database
On Mon, 31 Aug 2009, Lachlan Hunt wrote:
In the processing model, step 2 says:
If an error occurred in the opening of the transaction (e.g. if the
user agent failed to obtain an appropriate lock after an appropriate
delay), jump to the last step.
It's not clear if the spec
On Mon, 31 Aug 2009, Nikunj R. Mehta wrote:
In WebDatabase:
The user agent may raise a SECURITY_ERR exception instead of returning a
Database object if the request violates a policy decision (e.g. if the
user agent is configured to not allow the page to open databases).
In WebStorage
On Thu, 26 Nov 2009, João Eiras wrote:
Deleting all the data in the database (i.e. dropping all the tables)
should be sufficient, no? There's nothing to store if you don't have
any data in the database (in particular, there's no reason to store
the version as far as I can tell -- you
Would be much more simple to just delete the database explicitly
Yes, but is this something that will happen often enough to matter?
Unfortunately, that question has two answers. It should happen often, but
I doubt web developers will ever bother to clean up the data they don't
need :)
On Mon, 31 Aug 2009, Nikunj R. Mehta wrote:
There seems to be no difference between the openDatabase methods defined
in WindowDatabase and WorkerUtilsDatabase.
Is it possible to restructure these interfaces differently so that there
is less redundancy?
It would be, but since is a purely
On Mon, 31 Aug 2009, Nikunj R. Mehta wrote:
After studying the current error codes in the WebDatabase spec, it is
clear that they are neither an exhaustive, nor a systematic arrangement.
Indeed, they were added as needed.
As a result, applications will have a hard time performing recovery
On Thu, 26 Nov 2009, João Eiras wrote:
Would be much more simple to just delete the database explicitly
Yes, but is this something that will happen often enough to matter?
Unfortunately, that question has two answers. It should happen often,
but I doubt web developers will ever
On Wed, 25 Nov 2009, ATSUSHI TAKAYAMA wrote:
(Re-sending because I accidentally replied personally...)
Deleting all the data in the database (i.e. dropping all the tables)
SQLite 3 does not vacuum the database file when you drop a table.
http://www.sqlite.org/lang_droptable.html
That
During testing you can do it manually (why would you do it from code?).
Unit tests.
(Re-sending because I accidentally replied personally...)
Deleting all the data in the database (i.e. dropping all the tables)
SQLite 3 does not vacuum the database file when you drop a table.
http://www.sqlite.org/lang_droptable.html
If you repeat create and drop tables, you will hit the
On Wed, Nov 25, 2009 at 5:16 PM, Nikunj R. Mehta nikunj.me...@oracle.comwrote:
On Nov 24, 2009, at 7:40 PM, Ian Hickson wrote:
On Fri, 20 Nov 2009, Arthur Barstow wrote:
Based on the responses for this call for comments, I see the next steps
as:
1. Server-sent Events, Web Storage and
25 matches
Mail list logo
