Some of my slides are self-explanatory, some aren’t. Here is the slideshow with notes about each slide below.

Intro, yadda yadda

The web was designed in such a way that servers and clients don’t know about changes to the other except by the client making explicit requests (or by the server pushing updates via WebSocket or EventSource).

This lack of state prompted browser makers (pretty early on) to come up with cookies as a solution. It’s a technology that has served the web pretty well, but has some limitations, including being limited to 4KB and the fact that all of the state data is sent back and forth between the client and server on every request.

There is a better way.

It’s a bird! It’s a plane! It’s…HTML5!

I covered 3 technologies: Web SQL, localStorage, and sessionStorage. Each has different characteristics, which I likened to different kinds of vehicles. Web SQL is a giant dump truck because it’s kind of lumbering, but works well when you’re dealing with heaps of data.

localStorage is a Honda Civic because it’s way easier than Web SQL to use. It’s more nimble and easier for the average programmer to work with, but less flexible in what it can store.

sessionStorage is a Smart Car because it’s also nimble and easy to use, but has less range (to stretch the analogy). Specifically, the data stored in it goes away when the browser window is closed.

Next, I talked about browser support. Web SQL is supported on WebKit and Opera browsers; localStorage and sessionStorage are supported on more browsers, including Firefox 3.5 and IE8. IndexDB is currently only supported in Firefox 4, but it is, apparently, the future. (See the Q&A below for more detail about this.)

By understanding the characteristics of each technology, you can make an informed decision about how to use them in your projects. Persistent in this context means that the data survives between browser sessions, whereas sessionStorage is erased when the browser window is closed.

Demo time!

In this job market, the “we’re hiring” slide just has to be done. Email me if you have what it takes to work here!

Working Code Trumps All

Phil Dodds used to say “Working code trumps all theories.” It is in that spirit that I offered the following 2 demos, one of localStorage, the other of Web SQL. Have a play and feel free to ask questions about them in the comments.

Q&A

Folks asked some great questions during the presentation, only some of which I was able to answer. I’ve done a bit of research on the ones I can remember. Again, please jog my memory in the comments if I’ve forgotten any.

Isn’t the Web SQL API deprecated?

Turns out this API is, in fact, deprecated. According to this working group note (last updated November 18, 2010), the specification is at an impasse because, while WebKit and Opera agreed to use SQLite, Mozilla and Microsoft balked. The IndexDB specification appears to be blessed by the W3C, but it is in flux and only just showing up in browsers (most notably Firefox 4). Web SQL is likely to live on for some time, at least in WebKit, because of its utility as a way of enabling offline apps on mobile devices.

How secure is parameterized SQL?

David Schachter, who attended the Meetup, clarified after my presentation that the way in which parameterized SQL is safer is that it is not vulnerable to SQL injection attacks. That doesn’t mean you’re out of the woods! You should not trust values saved in this way when pulling them from your database (by, for example, injecting unsanitized strings into the innerHTML property of a DOM object).

How much faster is localStorage than Web SQL?

OK, so no one actually asked this. I did mention a couple of times that both localStorage and sessionStorage are significantly faster than client-side databases. If I’d had more time, I would have shown this speed comparison that shows just how much faster (spoiler alert: it’s around 3 orders of magnitude).