I’m between contracts at the moment so taking the opportunity to play with some bleeding edge technology. With it seeming like everyone’s jumping on the HTML5 bandwagon, even microsoft with windows 8, seemed like a good opportunity to restart my side project playing with the latest web tech.
So there’s a few things to note if you pick up indexedDB.. It’s bleeding edge and to be expected but here’s my experiences over the last week.
IndexedDB is in webkit (chrome) and firefox but not yet in safari. The database visualisation in the webkit developer tools isn’t linked in yet so you can’t mange the database that way yet. You can’t delete a database programmatically yet in either chrome or firefox. If you’re writing unit tests this is going to be a bit of a pain ;). Also you can’t yet access the indexedDB from webworkers. At this stage it’s attached to the window. One of the things I’m playing with is a stemming and text sorting index which was all running via webworkers. It’s an easy workaround, you just take the results from the webworkers and at a convenient time, merge and store instead of doing it directly. Still, will be cool when this works.
I’m sure these will be addressed pretty shortly, I’m running chrome alpha and dev channels, ffox 5 and will post back when I notice a change.