Portal Classes
BasicUser
Base class for all User objects
BasicUserFolder
Base class for UserFolder-like objects
MemberBase
This class is intended for use a a base class for a Z Class
to provide enhanced User-like objects. It provides only a slight
trace of extra authentication support. It may eventually provide
some default implementation.
MemberFolderBase
This class is intended for use as a base class for a Z Class
that implements access control and member data storage using
http cookies.
It provides basic validation support. It does *not*
provide member storage or management.
PortalObjectBase
The PortalSite mix-in provides:
- basic UIs for user registration, logging in, logging out, etc.
- virtual-host support
MemberInterface
A portal member object could be implemented ain a number of ways. It could subclass the Zope User class and use propertysheets to manage properties. Alternatively, it could be implemented via SQL or LDAP data and brains. In any case, the implementation must implement this interface.
MemberFolderInterface
This interface defined the hooks that a member folder needs to implement. It abstracts away details of user storage.
Note that it's doesn't specify a management UI for management of users by site managers.
xxxMemberFolder
A portal site has to implement an object like this one. A portal site should probably also
provide a UI, for use by site managers, for managing users, which isn't specified
here.
xxxPortal
For a particular portal site, implement an object with these methods plus any methods needed for the specific application.
(Note that this should probably have been modeled as an interface.)