On Dec 3, 2009, at 9:19 AM, Jeremy Orlow wrote:
Thanks Art and Nikunj!
Overall, I think it looks great. There are a few things I'd suggest
we change for WebStorage:
StorageEvents should be mentioned. They're actually one of the
greatest strengths of the WebStorage API.
You are right. I planned to include this in the comparison but the
Ctrl + E key handler in the Wiki disturbed me enough times that I
missed it. Now it has been added. Please take a look and change as you
see fit.
Right now, there's a no for atomicity, concurrency-error-free
operation, etc. I think this at least deserves a * that explains
this is only a problem with browsers that have multiple event loops
and there is a solution that's spec'ed but not implemented.
Fine by me.
Also the text introducing the DataCache APIs introduction is right
above the text of the AppCache's introduction.
Is there a change you are proposing?
Is there any chance this page could be linked from the various specs?
Thanks,
J
On Wed, Dec 2, 2009 at 3:23 PM, Arthur Barstow
<[email protected]> wrote:
A few weeks ago, WebApps' was asked "to rationalize and explain how
the [various Database-related] APIs fit together".
Thanks to some good work by Nikunj, we now have a wiki for this
purpose:
[[
http://www.w3.org/2008/webapps/wiki/Database
The purpose of this document is to provide a short summary regarding
the relationships between WebApps' database-related specifications.
By relationships in this context, we mean for example, are some
specifications complimentary, are some specifications competing, do
any of the specs specify overlapping functionality, etc. The
summaries are high-level yet they do articulate the key
relationships between these specs.
Status of this Document: this document is a Work In Progress and the
contents do NOT necessarily reflect the consensus of the WebApps
Working Group.
...
]]
As with all of our wiki documents, all WG members are encouraged to
update and maintain this document.
-Art Barstow
Nikunj
http://o-micron.blogspot.com
