-----BEGIN PGP SIGNED MESSAGE-----
Wichert Akkerman wrote:
> Previously Miles wrote:
>> We have quite a lot of copy-and-paste code here in order to support
>> using a custom MemberData class for members in particular sites.
>> The reason for this is that the only way to use a different MemberData
>> class is to provide a custom wrapUser method.
>> I'd like to propose that this is changed to use a factory registered
>> through the CA to create new MemberData objects, in order that this is
>> pluggable without requiring a custom MemberDataTool.
> Can you explain the use case? I suspect you can also solve this with PAS
> and a custom user factory PAS plugin.
"Member data" is wildly different from "user properties": memberdata is
about stuff local to a site, which is not required to have its own PAS.
Think of "member data" as being local annotations keyed by user ID, not
as being tightly coupled to the user from PAS.
(The fact that Plone forces the site to have its own PAS instance blurs
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope-CMF maillist - Zope-CMF@lists.zope.org
See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests