Client Side Storage Engine and OpenLayers

Using Client Side Storage for Mapping — a proof of concept which saves locally drawn features either via HTML5 Offline Storage or the same from Google Gears.

3 Responses to “Client Side Storage Engine and OpenLayers”

  1. Regina Says:

    This does look pretty neat. It will be nice to see native support for HTML 5 make it into browsers. I hope we don’t have to wait till 2012 (expected time of W3C Candidate Recommendation stage) before we see native implementation of this in browsers. Anyrate even if it requires an install of some sort, I guess its not too big of a deal.

  2. Regina Says:

    This does look pretty neat. It will be nice to see native support for HTML 5 make it into browsers. I hope we don’t have to wait till 2012 (expected time of W3C Candidate Recommendation stage) before we see native implementation of this in browsers. Anyrate even if it requires an install of some sort, I guess it is not too big of a deal.

  3. Max Says:

    Would it be possible to use this approach to also store raster data like map tiles on the client-side?