[Zope3-checkins] CVS: Zope3/src/zope/security - readme.txt:1.4.20.1
Chris McDonough
chrism at plope.com
Wed Jan 14 01:38:22 EST 2004
Update of /cvs-repository/Zope3/src/zope/security
In directory cvs.zope.org:/tmp/cvs-serv31942/src/zope/security
Modified Files:
Tag: steveachrismcd-securitypolicy-branch
readme.txt
Log Message:
Tease out some of the last bits of the role machinery from the zope/app and zope/security packages. What remains: translation files and some various page templates.
=== Zope3/src/zope/security/readme.txt 1.4 => 1.4.20.1 ===
--- Zope3/src/zope/security/readme.txt:1.4 Thu Jul 31 12:50:56 2003
+++ Zope3/src/zope/security/readme.txt Wed Jan 14 01:38:21 2004
@@ -12,8 +12,7 @@
Principal
- A generalization of a concept of a user. A principal may be
- associated with different roles and permissions.
+ A generalization of a concept of a user.
Permission
@@ -21,12 +20,6 @@
WRITE. Fundamentally the whole security framework is organized
around checking permissions on objects.
- Roles
-
- Represents a responsibility of a user in the context of an
- object. Roles are associated with the permissions necessary to
- fulfill the user's responsibility.
-
Purpose
The security framework's primary purpose is to guard and check
@@ -303,11 +296,10 @@
A Zope3 programmer will never commonly need to interact with the
low level security framework. Zope3 defines a second security
- package over top the low level framework that implements concepts
- of roles, and authentication sources and checkers are handled
- via zcml registration. Still those developing Zope3 will
- hopefully find this useful as an introduction into the
- underpinnings of the security framework.
+ package over top the low level framework and authentication
+ sources and checkers are handled via zcml registration. Still
+ those developing Zope3 will hopefully find this useful as an
+ introduction into the underpinnings of the security framework.
Code
More information about the Zope3-Checkins
mailing list