• Earn a $50 Amazon gift card for testing a new product from the makers of PBworks. Click here to apply.

  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

View
 

The Next Web Preso Wiki AK*2

Page history last edited by PBworks 12 years, 2 months ago

http://www.barcamp.org/svwb_schedule

Web Building Track 7:00pm

The Characteristics of the Next Web (3.0?)Architecture! What is Dashboard Serveware and what Web 2.0 problems {Like more Users leading to better App Performance not Worse!} will it solve for the next generation of Web Developers & Users!?! An Interactive Presentation & OPEN discussion moderated by AK*2

 

Using Dashboard Serveware HTML 5 client-side (Local) & In Memory Databases to Solve some of the Performance & Security Evolutionary Dead Ends that the Server Client Web 2.0 Mindset is leading us to.

 

http://webkit.org/blog/

WebKit Does HTML5 Client-side Database Storage

Posted by bradeeoh on Friday, October 19th, 2007 at 4:04 pm

 

The current working spec for the HTML5 standard has a lot of exciting features we would eventually like to implement in WebKit. One feature we felt was exciting enough to tackle now even though the spec is still in flux is client-side database storage. So for the last few weeks andersca, xenon, and I have been cooking up an implementation!

 

The client-side database storage API allows web applications to store structured data locally using a medium many web developers are already familiar with - SQL.

 

The API is asynchronous and uses callback functions to track the results of a database query.

Compact usage defining a callback function on the fly might look something like this:

 

var database = openDatabase("Database Name", "Database Version");

 

database.executeSql("SELECT * FROM test", function(result1) {

// do something with the results

database.executeSql("DROP TABLE test", function(result2) {

// do some more stuff

alert("My second database query finished executing!");

});

});

 

There will also be a small example of how to use the API in a real site that we'll try to keep up to date as things evolve.

 

This initial implementation has some things missing from the spec as well as a few known bugs. But it does the basics and the best way to discover what needs work is to get it out there for people to start using it!

 

If you find any bugs, would like to suggest features, or have gripes about the spec itself, please drop by #webkit or drop us a line on the WebKit email lists.

 

Oh, and one more thing…

 

We're landing this initial implementation with pretty cool Web Inspector support!

So far you can view the full contents of any table and run arbitrary queries on each database a page is using. We have a lot of ideas for improvements but would also love to hear yours.

DatabaseInspector