1) put them in the datastore and memcache the mostly commonly used
(like the tiles at the startup level)
2) set client side cache headers for the tiles if they don't change
often
3) use alternative storage like Amazon S3

personally, i would not try the datastore method first. I have not
seen an issue yet with storing tiles as blobs

cheers
brian

On Sep 2, 12:09 pm, Fred <[EMAIL PROTECTED]> wrote:
> Tim:
>
> > why aren't you storing your tiles as entities in the store rather than
> > as files?
>
> I was concerned about CPU quotas - each tile request would hit the
> datastore.
>
> On Sep 2, 5:03 pm, Tim Hoffman <[EMAIL PROTECTED]> wrote:
>
>
>
> > why aren't you storing your tiles as entities in the store rather than
> > as files?
>
> > T
>
> > On Sep 2, 11:29 pm, Fred <[EMAIL PROTECTED]> wrote:
>
> > > Hi,
>
> > > I'm developing a google maps app, hosted on GAE, for which I've
> > > developed a custom tile overlay, consisting of thousands of png
> > > images, at about 4 - 8k each in size. I've tried uploading about 15mb
> > > worth of tiles (just over 3,500 tiles), and have hit the 1000 file
> > > limit. (Detailed in issue 161 
> > > -http://code.google.com/p/googleappengine/issues/detail?id=161
> > > ).
>
> > > The suggestion from google is: "We encourage developers to find
> > > creative ways to reduce the number of files in an app" - but for a
> > > custom overlay in maps I don't think there is any other solution that
> > > to have multiple tiles.
>
> > > So - my question is whether anyone can suggest a way around this. I
> > > think this is a showstopper for me otherwise.
>
> > > Thanks!- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to