I think this would be harder than it sounds. With my own testing on this, EVERY address the application accesses needs to be covered in one section or another of the cache-manifest file. Also, by doing this, your users wouldn't get updates to the maps API until you updated your cache-manifest file.
Although, I did briefly toy with the idea myself. Chad Killingsworth On May 12, 12:54 pm, Nick Smith <[email protected]> wrote: > Does it make sense to build a list of javascript files and commonly > used images by the Maps system and place them in the HTML5 > cache.manifest file for a mobile app? > > Obviously no point caching map tiles, but the core javascript library, > marker images, etc. perhaps? > > Thanks > > -- > You received this message because you are subscribed to the Google Groups > "Google Maps JavaScript API v3" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/google-maps-js-api-v3?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
