1. If you absolutely have to have all 6,500 city names for each user session, I would put them in a separate JavaScript file, stick a reference to it at the bottom of your app page, and host this file somewhere outside of GAE to save a bit of money. This file will be cached by browsers, so that returning visitors most likely won't have to load it again.
2. Now, I very much doubt that your users click/browse/view more than a dozen cities during their visit. I cannot come up with any use case why you need to load all 6,500 names for each visitor. Users will never look at more than 50 records. If you need to load/display more than 50 city names at a time, you have the wrong data model or bad app design. -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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-appengine?hl=en.
