Memcache's data is not persistent and may lose at any time, so it depends what's the session is used for. A combined version should work, however the advantage isn't clear. Unless there is a lot read access without write back. Even that I believe datastore read is already cached by google.
On Oct 24, 6:19 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > What are the advantages or disadvantages of using memcache for > sessions? > I see that other people are implementing both approaches combined, > although the ones I tested are buggy. > > And by the way, Is it possible to create a GAE branch with Yejun's and > Anand's patches? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
