Jay, In general, no there are not limitations on App Engine's HttpSession. Here are some things that are useful to know, though:
1) They aren't enabled by default. You need to turn them on<http://code.google.com/appengine/docs/java/config/appconfig.html#Enabling_Sessions>in appengine-web.xml. 2) They are distributed and persistent. This means that the objects you stick in them need to be Serializable. This is no different from any other container that supports clustered or persistent HttpSessions. There is an outstanding issue that our dev_appserver doesn't require HttpSession values to be Serializable like prod. 3) App Engine does not serialize requests to the same HttpSession. That behavior is a deviation from the standard. On Thu, Sep 24, 2009 at 8:55 AM, Jay Damon <jdam...@gmail.com> wrote: > > I am relatively new to App Engine. Recently I have starting seeing > indications that there are limitations? on the the use of HTTP > sessions in App Engine? For example, I see that there is a > gaeutilities project that provides a class Session: An http session > class to preserve identity across http requests. Are there > limitations on HTTP sessions in App Engine? If so, what are those > limitations? If not, what specific issues does the gaeutilities > project class address? Many of the limitations in App Engine concern > me but any limitations at all on HTTP sessions would be a showstopper > for me. > > > --~--~---------~--~----~------------~-------~--~----~ 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 google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
