You can use memcache to help speed up access to the DB. All communication over GAE has to be done using HTTP... So, that makes it harder to things like pushing real time messages to the clients. You can use a technique called "Long Polling", but requests must return in 30 seconds, and currently, applications have a max of 30 simultaneous requests.
Basically, the request starts a thread that sleeps most of the time, waiting to return data to the client when it's ready. One the client receives the update, it makes another long polling request. Hope this helps. - Derrick On Feb 28, 2:58 am, Ahmed Khalifa <[email protected]> wrote: > hi all, > I am writing a multiplayer flash arcade game in actionscript .. i have > discovered GAE recently and thought that it might be a very good > choice for building and hosting my server .. > however, i realize that arcade games need an almost realtime > responsive capacity from the server .. besides the server has to be > looping on receiving position object of Client A, storing it in a DB, > Fetching Client B position object and sending it back .. this will > result in a huge number of DB requests either storing, fetching or > deleting which will quickly exhaust the CPU quota for the > application .. > > So, I was wondering if any one had an idea or a reference to come > around these two problems of real time response and CPU exhaustion by > DB calls > > best regards, > A. Khalifa -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
