See http://code.google.com/p/gmemsess/ for a memcache-based session class.
Memcache is fine for short-lived sessions, which must persist for hours. This is good for authentication and shopping cart applications, but if you need the user data to be available after several days/weeks/ months then you need datastore-based sessions. I use gmemsess for authentication in commercial applications, and have had no problems with it. On Nov 11, 9:05 pm, 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] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
