gwt-comet has some support for GAE, the primary issues with GAE is that HTTP sessions are not sticky to a particular node. GAE only allows a HTTP response to be open for 30 so when the connection gets refreshed it may end up on a different node. This causes problems with message queueing and routing on the server side. I've done some initial work on using the data store to queue messages so when the connection migrates to a different node the messages in the data store can be fetched by the new node.
I would very much like to improve gwt-comet's support for GAE. Another issue that needs to be looked into is how the pricing works. Do they charge for 30 seconds of CPU per request even though the thread processing the request is mainly idle? >From Richard. On Mar 5, 1:56 am, Thomas Broyer <[email protected]> wrote: > On Mar 4, 10:30 am, mariyan nenchev <[email protected]> wrote: > > > Hi, > > > Is it possible to use app engine with some server push framework? Could > > you suggest any? > > Have you looked > athttp://code.google.com/p/google-web-toolkit-incubator/wiki/ServerPushFAQ > (don't forget the comments) > > Here are two free "comet" implementations with special handling for > AppEngine (though I don't know the impact on pricing once > deployed)http://code.google.com/p/gwt-comet/https://atmosphere.dev.java.net/ > > But I'd rather ask the appengine group if I were you... -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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-web-toolkit?hl=en.
