这儿的问题是现有应用通过实现数据存取和验证逻辑有效控制了企业数据的访问。
The issue here is that existing applications effectively control enterprise data access through implementation of the data access and validation logic.
这种逻辑对于大量更新访问控制配置的情况特别有用。
This logic especially makes sense in scenarios with many updates of the access control configuration.
控制逻辑利用COM对象(3)来访问数据库。
The control logic makes use of COM objects (3) to access the database.
除了简单地提供商务逻辑之外，应用程序必须支持访问安全控制，数据持久化，事务，和其它的进阶功能。
Beyond simply providing business logic, applications must support secure access, persistence of data, transactional behavior, and other advanced features.
根据要实现的业务逻辑定义Portlet交互和访问控制。
Define portlet interaction and access control according to the business logic to be implemented.
PQ96873这种逻辑对于大量更新访问控制配置的情况特别有用（尤其是在角色分配和取消分配时）；否则，应该为false。
PQ96873 This logic especially makes useful in scenarios with many updates of the access control configuration (especially role assignments and unassignments), otherwise, should be false. false
现在我们的应用程序流控制逻辑从控制器开始，数据库访问逻辑由repository负责，现在我们要把验证逻辑放在哪里呢？
So, application flow control logic belongs in a controller and data access logic belongs in a repository. In that case, where do you put your validation logic?
将服务定义同业务逻辑(控制器)以及数据(实体)访问分离，可确保实体中不会透露任何业务逻辑。
Decoupling the service definition from the business logic (controller) and from access to the data (entity) ensures that no business logic manifests itself in the entities.
注意：理想情况下，可以将数据访问逻辑分隔到它自己的部署单元中并且保持控制器没有被混杂。
NOTE: Ideally, you could separate the data access logic into its own deployment unit and keep the controller pure.
如果系统的资源逻辑上是有组织的，那么可以创建更多的组来更好地控制对资源的访问。
If resources are logically organized on the system, then create more groups to finely tune access to resources.
控制器将访问其他服务或通过其创建、读取、更新和删除 (CRUD)操作访问后端实体，从而实现服务业务逻辑。
The controller implements the service business logic by accessing other services or accessing backend entities via their create, read, update and delete (CRUD) operations
因为开发人员完全控制在会话bean中使用的数据访问机制，所以可以针对某些任务优化数据访问和持久性逻辑。
Because developers have complete control over the data access mechanism used within a session bean, data access and persistence logic can be optimized for certain tasks.
针对开发人员，“Geneva”通过使用声明的方式来控制用户对程序的访问权限，通过使用预先构建好的安全逻辑与集成的.NET工具来减少开发工作量。
“Geneva” helps simplify user access for developers by externalizing user access from applications via claims and reducing development effort with pre-built security logic and integrated .NET tools.
文章重点讨论了安全标签的设计思想、传输策略和访问控制逻辑，然后给出系统策略配置管理平台的设计和实现。
We mainly analyse design methodology, Transmission strategy and Access Control logic of Security Label. Then we present the design and implementation of Policy Configuration and Management platform.
而基于角色的访问控制模型以角色为中介，将用户与权限逻辑隔离，但该模型不能处理有执行顺序的任务；
Role is introduced to separate user and privilege in role-based access control model, but RBAC can't directly control the permission for a sequence of events.
模型引入客体与客体的关联，使得权限既可以通过角色也可以通过客体获得，并采用描述逻辑对模型访问控制过程进行了形式化描述。
In the model an associated object was presented, so the permissions can be obtained through roles and objects. The access control processes were described with the description logic.
针对基于SSL的安全通信模型中ssl握手协议部分在访问控制方面的缺陷，本文提出了一个基于pmi的全解决方案，并对改进设计进行了分析和BAN逻辑证明。
As for the flaws of the SSL handshake protocol part in the SSL based security communication model, the thesis proposes a PMI based solution and analyzes the design by using the BAN logic.
本文通过对业务逻辑的抽象与提取，形成了通用数据库访问控制框架及在此框架下的访问控制要素的聚类模型。
Based on generalized framework for access control, the author has developed an application model on universal database by conceptual and extract business logics.
提出了一种基于委托逻辑的访问控制模型——dlbac，将凭证、RBAC元素和访问策略转化为统一的委托逻辑规则。
The paper puts forward a delegation logic based access control model (DLBAC). It translates the credentials, RBAC elements and access policies into unified delegation logic rules.
您应该公开组件的属性而不是公共字段，因为属性的版本可以控制，它们允许数据隐藏，并且访问器方法可以执行附加逻辑。
You should expose properties instead of public fields from your components, because properties can be versioned, they allow data hiding, and the accessor methods can execute additional logic.
提出一个基于逻辑程序和基于角色访问控制并且具有柔性授权、逻辑形式化和策略集成特点的柔性授权框架。
A flexible authorization framework based on logic programs and RBAC, with flexible authorization, logic-based formalization and integration of policies, was proposed.
本通信协议分为物理层、介质访问控制层和逻辑链路控制层三层设计。
The communication protocol is designed in term of three layers: Physical layer, Media Access Control layer and Logic Link Control layer.
本通信协议分为物理层、介质访问控制层和逻辑链路控制层三层设计。
The communication protocol is designed in term of three layers: Physical layer, Media Access Control layer and Logic Link Control layer.
应用推荐