Consider looking here: http://code.google.com/appengine/docs/java/config/appconfig.html
You can enable HTTP sessions. The cookie that is sent to a user is used to identify the session, and no session variables are actually stored in the cookie. Underneath the hood, objects are serialized and stored in Memcache. On Wed, Nov 11, 2009 at 12:05 AM, PeeCee <[email protected]> wrote: > > we're building a google app in which we need to handle the sessions. > But if I do not want to use session which uses cookies and instead > want to use memcache, then I should use it or not? > If I should, then how? > and what's the risk? > > Any help will be appreciated.. > > Thanks in advance. > > --~--~---------~--~----~------------~-------~--~----~ > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en > -~----------~----~----~----~------~----~------~--~--- > > -- Ikai Lan Developer Programs Engineer, Google App Engine -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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?hl=.
