« OpenLayers 2.6 Release
Using TileCache with Google Maps, Virtual Earth »

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.

This entry was posted on Tuesday, April 15th, 2008 at 9:26 pm and is filed under Locality and Space, OpenLayers. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

3 Responses to “Client Side Storage Engine and OpenLayers”

  1. Regina Says:
    April 17th, 2008 at 3:37 am

    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:
    April 17th, 2008 at 3:37 am

    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:
    January 21st, 2010 at 3:31 am

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