我应该在Google App Engine中使用会话吗? [英] Should I use sessions in Google App Engine?

查看:55
本文介绍了我应该在Google App Engine中使用会话吗?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我刚刚从此问题中学到了Google App Engine现在支持的会议.我希望能够使用它们,但是不确定是否可以使用它们.多亏可扩展性问题.

I have just learned from this questions that Google app Engine now supports session. I would like to be able to use them but am not sure whether I should just because I can. Thanks to scalability issues.

我的问题是真的

我将会话信息存储在哪里?在数据存储中还是需要很长时间?而且肯定要付出高昂的代价吗?

Where would I store the session information? In the data store or would this take to long? And surely far to costly?

那内存缓存呢?我只有几天才知道GAE,现在仍在阅读.Mem高速缓存是否被认为是快速/可伸缩的,是否需要费用?

What about the mem cache? I have only known of GAE for a few days and am still reading. Is the Mem cache considered to be fast/scalable and does it cost?

使用会话进行可伸缩性的最佳做法是什么?

What is the best practice for scalability with sessions?

非常感谢

推荐答案

您真的没有选择.Appengine透明地为您处理会话持久性和快速访问.

You don't really have a choice. Appengine handles session persistence and fast access for you, transparently.

官方文档的报价:

App Engine包括使用servlet会话接口的会话实现.该实现将会话数据存储在App Engine数据存储区中以实现持久性,并且还使用内存缓存来提高速度.

App Engine includes an implementation of sessions, using the servlet session interface. The implementation stores session data in the App Engine datastore for persistence, and also uses memcache for speed.

这篇关于我应该在Google App Engine中使用会话吗?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆