Session isn't lost but session use is discouraged. You have memcache
which is pretty fast in retrieval. Of course, every once a while even
the memcache can be invalidated due to various reasons. While relying
on memcache you need to be sure that in case the value returned is
null query the
can anybody provide good link for dos and donts for high traffic apps ?
On Sun, Jun 13, 2010 at 11:52 AM, nischalshetty
nischalshett...@gmail.comwrote:
Session isn't lost but session use is discouraged. You have memcache
which is pretty fast in retrieval. Of course, every once a while even
Google appengine stores session data in the App Engine datastore for
persistence, and also uses memcache for speed. Using the AppEngine
implementation of sessions for Java, you are using a combination of
datastore and memcache and this solution is transparent from the
development point of view.
Session is cached in memcache and persisted to datastore. So when
loading request occurs it won't be lost if it is not expired. You can
view session (_ah_SESSION) data with datastore viewer.
On 6月11日, 下午11時09分, Rahul rahul.jun...@gmail.com wrote:
No doubt if your application is low traffic you
No doubt if your application is low traffic you will definitely need
memcache as session will be lost every minute when the jvm restarts
and you need to reload everything and also session is highly
discouraged due to various reasons.
Thanks,
Rahul
On Jun 11, 4:16 am, RAVINDER MAAN
I was not aware about loss of session objects.strange!!
On Fri, Jun 11, 2010 at 8:39 PM, Rahul rahul.jun...@gmail.com wrote:
No doubt if your application is low traffic you will definitely need
memcache as session will be lost every minute when the jvm restarts
and you need to reload
