However, in some situations, it might make sense to define your own code access permission class.
但在某些情况下,定义自己的代码访问权限类可能会有用。
These permission classes are described briefly in the Permissions topic and in detail in the reference documentation for each permission class.
在权限主题中对这些权限类作了概括描述,在每个权限类的参考文档中提供对该权限类的详细描述。
In general, you should design your permission class so that the state of the permission is as complex as necessary, without greatly impacting performance.
一般情况下,在设计权限类时,应当按需要确定权限状态的复杂程度,从而不会对性能造成很大影响。
When a built-in code access permission class protects a resource but does not sufficiently control access to that resource, you might need a custom code access permission.
如果内置代码访问权限类保护一种资源但不能充分控制对该资源的访问,则您可能需要使用自定义代码访问权限。
The runtime queries the Permission class about its implication reasoning logic by calling a method, aptly named implies.
运行时通过调用一个恰当地取名为implies的方法来查询permission类的隐含推断逻辑。
However, the runtime cannot be expected to make any further judgments and must delegate this implication reasoning logic to the Permission class in question.
不过,不能指望运行时进行进一步的判断,并且必须将这种隐含推断逻辑指派给所涉及的permission类。
However, the runtime cannot be expected to make any further judgments and must delegate this implication reasoning logic to the Permission class in question.
不过,不能指望运行时进行进一步的判断,并且必须将这种隐含推断逻辑指派给所涉及的permission类。
应用推荐