Thursday, March 18, 2010

Re: [google-appengine] Session Data must be in DataStore?

Guy,
Memcache is shared across instances. But it is a cache... so items
may be cleared at any time. If you have short lived sessions and
having one or more get cleared from time to time is not a problem use
memcache.

Check out gaeutilities. It makes working with sessions pretty easy.

Robert


On Mar 18, 2010, at 8:41, Guy Smith <guy@multiniche.org> wrote:

> "If a web application wants to store session data, then it must be
> stored in the DataStore rather than static variables or MemCache."
> -
> is that correct?
>
> I understand the reasoning behind it – that separate requests in a
> session may go to different servers, which will not have the same
> values in static variables or MemCache, only the DataStore is shared
> between servers. But it is expensive (in developer time and DataStore
> writes), so I'd just like to double check.
>
> NB: I have a fair bit of session data – encoding it in the cookie is
> not feasible.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Google App Engine" group.
> To post to this group, send email to google-
> appengine@googlegroups.com.
> To unsubscribe from this group, send email to google-appengine+unsubscribe@googlegroups.com
> .
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en
> .
>

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to google-appengine+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

No comments:

Post a Comment