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?

我可以看到一个明显的原因：向后兼容性。这是Adobe的典型。同时我怀疑Adobe关心与其他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设置为是，那么仍会创建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屋！