ColdFusion 中 J2EE 会话管理的缺点 [英] Disadvantages of J2EE session management in ColdFusion

问题描述

手册页面 讲述了 J2EE 会话管理 (SM) 相对于 ColdFusion SM 的诸多优势，但另一方面呢?使用 J2EE SM 会出现哪些问题?

Manual page tells about bunch of advantages of the J2EE session management (SM) over the ColdFusion SM, but what about other side? Which problems can appear when using J2EE SM?

另外，如果 J2EE SM 这么酷，为什么 ColdFusion SM 仍然是默认的?

Also, if J2EE SM is so cool, why ColdFusion SM is still default?

我可以看到一个明显的原因:向后兼容性.这对 Adob​​e 来说很典型.同时我怀疑 Adob​​e 是否关心与其他 CFML 引擎的兼容性.

I can see one obvious reason: backwards compatibility. And this is typical for Adobe. Same time I doubt that Adobe cares about compatibility with other CFML engines.

还有其他原因吗?

推荐答案

我没有找到，真的.J2EE 会话管理一出现，我就开始使用它并且没有遇到任何问题.

None that I've found, really. As soon as J2EE session management became available I started using it and have had no troubles.

我遇到的唯一问题是，即使您打开 J2EE 会话管理，如果您将setclientcookies"设置为 yes，CFIDE/CFTOKEN cookie 对仍然会被创建.这在我当前的环境中造成了一个问题，因为有一项针对持久性 cookie 的政策.

The only problem I had with it was that even if you turn on J2EE session management, if you "setclientcookies" to yes the CFIDE/CFTOKEN cookie pair is created anyway. That caused a problem in my current environment as there is a policy against persistent cookies.

我想如果您需要在浏览器关闭并重新启动时保持会话可用，那么 J2EE 会话管理不适合您.

I suppose if you have a need for a session to remain available if the browser is closed and restarted then the J2EE session management isn't for you.

这篇关于ColdFusion 中 J2EE 会话管理的缺点的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！