route-me-map
[Prev] Thread [Next] | [Prev] Date [Next]
[route-me] Re: serious performance issue with cache directory, also rejection hiccup Matt Farnell Wed Jun 17 11:00:35 2009
Thanks Hal, Isn't having it in Documents because it syncs a good thing? Then on upgrades the cache is still available. So from the selfish perspective or apps wouldn't that be a good thing? On Wed, Jun 17, 2009 at 10:16 AM, Hal Mueller <[EMAIL PROTECTED]> wrote: > If you have a shipping app (or even more importantly, a close-to-shipping > app), pay special attention to > http://code.google.com/p/route-me/issues/detail?id=109: > > The existing FMDB/SQLite tile cache stores its data in a subdirectory of > ~/Documents. > > ~/Documents is backed up when the iPhone syncs. Apple recommends using > ~/Library/Caches for > any cache data that can be regenerated; that folder is not backed up. > > > Each cache, for each tilesource, is backed up on each sync. This makes the > syncs quite slow. Apple best practices says to put any data that can be > regenerated into ~/Library/Caches, which is not backed up. > > If you haven't shipped yet, just switch the folder that FMDB uses. This > probably needs to be done on both the trunk and a branch for 0.5 (we're > picking up other 0.5 patches, might end up pushing a 0.51); any volunteers > to do this? > > If you have shipped, it's more complicated. You already have a cache in > ~/Documents. Simply changing the FMDB code won't be enough. You'll have to > push a new version that cleans out the old cache(s) in ~/Documents. If you > have changed the unique tilesource identifier, you'll have even more dead > data in there. > > Another point: at least a couple of us have received rejections from Apple > for not handling the case of no network connectivity on app launch. In my > case, I was presenting a mostly blank screen if no tiles could be > downloaded and the cache was blank. It's simple to add an alert for this > case (following the Reachability sample code) instructing the user to > connect to a network. > > I'll be sending out a longer WWDC summary today or tomorrow, but wanted to > get this in front of everyone right away. > Hal > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "route-me" 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/route-me-map?hl=en -~----------~----~----~----~------~----~------~--~---
- [route-me] serious performance issue with cache directory, also rejection hiccup Hal Mueller
- [route-me] Re: serious performance issue with cache directory, also rejection hiccup Matt Farnell <=
- [route-me] Re: serious performance issue with cache directory, also rejection hiccup Tracy
- [route-me] Re: serious performance issue with cache directory, also rejection hiccup Hal Mueller
- [route-me] Re: serious performance issue with cache directory, also rejection hiccup Matt Farnell
- [route-me] Re: serious performance issue with cache directory, also rejection hiccup Hal Mueller
- [route-me] Re: serious performance issue with cache directory, also rejection hiccup David Clements
- [route-me] Re: serious performance issue with cache directory, also rejection hiccup Matt Farnell
- [route-me] Re: serious performance issue with cache directory, also rejection hiccup Henri Asseily
- [route-me] Re: serious performance issue with cache directory, also rejection hiccup David Clements
- [route-me] Re: serious performance issue with cache directory, also rejection hiccup Ivo Brodien
- [route-me] Re: serious performance issue with cache directory, also rejection hiccup David Clements