Correct me if I'm wrong, but memcache is purely memory only whereas Session is persisted to the datastore for the life of the session which may involve multiple servers depending on routing of your requests. This would be typical Session behavior for Clustering. Whereas memcache can be refreshed anytime during your session, the actual Session data should survive for the full session. Naturally, memcache is faster access since NO datastore is involved. Sounds kinda obvious, I'm sure others add the not so obvious and enlighten both of us further.
On Aug 19, 2:46 pm, repairman <[email protected]> wrote: > hi I am writting a jsp application calling java classes to get data > from the gae database such as product information. I then save the > information into the session. so the question is what is the > difference between saving the data into session vs memcache? aren't > they the same conceptually? I guess memcache is common amongst all > sessions, is that the only difference? please give best practice. > > And also after I post to the forum does it automatically send me an > email if my posting is updated? or do I have to set some settings in > the subscription? > > thanks all. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en -~----------~----~----~----~------~----~------~--~---
