On Nov 11, 3: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?
I don't see cookie vs. memcache as an either/or choice; your
application needs to link a particular user to a session; whether the
session data is stored in memcache (which is only a good idea if your
users don't mind being logged out at random) or the datastore doesn't
have much to do with how you identify a request as being part of a
particular session. You pretty much either need to store a cookie or
add a session ID to URLs you're linking to. (You could also try using
the user's IP address to identify them, but if you have 2 concurrent
users with the same IP address because of a proxy or NAT setup, this
is going to be a huge problem).
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
