Right now, we're probably doing a double trip to the datastore. Once to get
the standard datastore-backed GAE HttpSession and once to access our custom
Session object. We should consider storing serializable content directly in
the HttpSession instead, via setAttribute() see:
http://code.google.com/appengine/docs/java/config/appconfig.html#Enabling_Ses
sions
Original issue reported on code.google.com by philippe.beaudoin on 3 May 2010 at 10:08
Original issue reported on code.google.com by
philippe.beaudoin
on 3 May 2010 at 10:08