I was intrigued by this tweet from Abraham Williams. I haven’t been paying too much attention to HTML 5, mostly because I think of HTML as pure presentation. My expertise is the server-side of applications, not the UI. My whole career I’ve been wondering when we’ll get to the nirvana that will let me concentrate on the business side of applications and let those who know UI build the UI that connects to the back end.
But in steps the aforementioned tweet talking about Chrome supporting IndexedDB. I was curious, so I started poking around on the W3C website. I found the Web Storage document, the Indexed Database API document, and the Web Sockets API document. Interesting. Web Storage and Indexed Database are both for storing data locally so that an application can work when not connected to a network. Web Sockets allows two-way communication between browser and server.
I have to wonder, though, if there is a limited lifetime for local storage in the browser. The day can’t be too far off when there won’t be the concept of being “disconnected” from the web. Coverage will be such that we’ll be able to be connected to the internet all the time, no matter where we are. Web Sockets is even more interesting to me. The browser concept was never supposed to allow two-way persistent communication. You make a request and receive a response, then you close the connection. We’ve devised all kinds of workarounds using server-side sessions, so I suppose this is the next logical step.
Sigh. I’d better start learning the finer points of UI design now.