Miles Waller wrote:
AFAICS, CMFMember covers two sets of requirements:
- put members through a workflow
Very useful.
- use archetypes to configure member objects which behave like
normal zope objects
I'm not familiar enough with archetypes to tell what the actual benefits
of this is.
On Mon, Nov 03, 2003 at 01:38:12PM +0100, Lennart Regebro wrote:
| Miles Waller wrote:
| AFAICS, CMFMember covers two sets of requirements:
|
| - put members through a workflow
|
| Very useful.
|
| - use archetypes to configure member objects which behave like
| normal zope objects
|
|
Sidnei da Silva wrote:
One of the benefits is to be able to plug your own storage
layer. There is a SQLStorage layer provided by default.
As I understand it, this would be useful if you want one field from an
SQL server and one from LAP, for example, but not if you want one user
from LDAP and
