> That's why I i'm going with this (which isn't fully realised yet): > - Generate tile as requested > - Cache that tile as a file, setting a flag that tells me it's been > generated > - Next time that tile is requested, serve it up directly without > having to process again, which should be fast.
While your method does sound reasonable, in practice (for an area like the US) it would be unlikely to work. The problem is that you would need a database pull on every tile regardless of if its been generated or not. Of course, if only 20 users are actually looking at your map in a day, then this will be fine but if you have 250,000 or more users downloading 30,000,000 tiles a month, you have to have things done in a more efficient manner. The only reasonable solution is to make the tile sets in advance and just serve them. For Australia though, you're probably ok, I would suggest though that instead of using a database to check the status of your tile, you simple check for the existence of the tile file and only open a database handle if you need to create a tile from scratch. -John Coryat http://maps.huge.info http://www.usnaviguide.com http://www.zipmap.net (~250,000 visitors, ~30,000,000 tiles delivered a month) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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-API?hl=en -~----------~----~----~----~------~----~------~--~---
