There isn't a straight-up answer to that. The question to ask is: Why do you think you need a server-side session? Depending on the answer, there are various solutions.
For example, if you're storing the authentication state of a user in the session, store it as a signed cookie instead. Easy. If you have some kind of per-user server-side state you are maintaining, stash it in memcache (if it is not essential) or the datastore (if it is). This is what the session does, except that with sessions you don't have granular control. You end up struggling with the performance profile because the behavior of sessions in a cluster is poorly defined - some people need super transactional robust behavior, others don't care if the data expires randomly. Jeff On Mon, Apr 16, 2012 at 3:27 PM, andrew <[email protected]> wrote: > As an ignorant, can I genuinely ask: > > What is the recommended equivalent implementation for apps with high > scalability needs (available in Java and NOT using a GAE API directly)? > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/OxttnQjWGMEJ. > 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. > -- 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.
