为什么人们不使用<CFLOGIN>? [英] Why don't people use <CFLOGIN>?

查看:25
本文介绍了为什么人们不使用<CFLOGIN>?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

为什么人们不使用 CFLOGIN?我记得几个月前 CF7 遇到过问题,但我不记得它出了什么问题.

Why don't people use CFLOGIN? I remember having problem with it with CF7 some months ago, but I couldn't remember what was wrong with it.

推荐答案

我一直在使用 cflogin,效果很好.以你喜欢的方式工作可能有点棘手,但好处是巨大的.能够使用用户角色微调您的应用程序可以处理我的大部分基于权限的自定义.过去,会话管理存在一些问题,使其难以处理.打开 j2ee 会话似乎可以解决大部分问题.

I use cflogin all the time and it works great. It can be a little tricky to get working the way you like, but the benefits are huge. Being able to fine tune your application with user roles takes care of the bulk of my rights based customization. There used to be some issues with session management that made it difficult to work with. Turning on j2ee sessions seems to make most of those issues go away.

一些流行的框架与 cflogin 不兼容,所以这可能是你看不到很多它的原因之一.他们往往有自己的方法来保护应用程序功能.

Some of the popular frameworks are not compatible with cflogin, so that might be one reason you don't see a lot of it. They tend to have their own approach to securing application features.

我认为很多人对此感到沮丧,因为它有点古怪,他们放弃了.其他人有更复杂的安全需求,cflogin 无法完全解决这些需求,因此他们最终编写了自己的系统.具体来说,按内容资产处理权利并不容易.

I think a lot of people get frustrated with it because it is a little quirky and they give up on it. Others have more complicated security needs that aren't addressed completely by cflogin, so they wind up writing their own system. Specifically, there isn't an easy way to deal with rights by content asset.

这篇关于为什么人们不使用<CFLOGIN>?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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