GAE only supports short-lived connections (about 30 seconds). This means that you cannot open a permanent connection between your client and the GAE server. This effectively prevents push notifications from server to client, which are necessary in most game settings.
To ease this limitation, Google has introduced the Channel API , which allows you to forward messages from the server to the client. However, you need to use your client side javascript library . You can write an applet that calls javascript to access this library, but it may be a little shredded.
All in all, due to these limitations, GAE may not be suitable for your needs.
Update:
There is another reason GAE is not suitable for real-time communication between users: a client request to the GAE application can be served by any server that Google chooses. Two users can connect to two different servers, even in different data centers (possibly even on different continents). In order to transfer data between them, you need to save all messages in the data warehouse (slow) or in memcache (unreliable and possibly slow, because it must be distributed between servers / data centers).
source share