Re: [Zope3-Users] Users need to activate their accounts

[Stephan Richter]

On Sunday 12 February 2006 15:42, Florian Lindner wrote:
> At the moment I tend to 1) or 3). What do you think? How do you do it?

I would prefer method 2) because it separates concerns best. The 
Authentication utility should not be misused to implement all the other 
features you need for your application. The PAS in Zope 2/CMF/Plone is an 
example where they stuffed more and more features into the PAS and now have a 
monolithic monster. So, to iterate my point, write a utility that is only 
responsible for holding registration information and use it to generate the 
principal information upon activation.

Regards,
Stephan
-- 
Stephan Richter
CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users

Re: [Zope3-Users] Users need to activate their accounts

[Florian Lindner]

Am Sonntag, 12. Februar 2006 21:42 schrieb Florian Lindner:
> Hello,
> how would you implement something like that?
>
> What comes into my mind is:
>
> 1) Let the registration script create a PendingPrincipal object and store
> them into a folder. The activation script create a real user in the PAU
> based on the PendingPrincipal und deletes the PendingPrincipal.
> Can I reuse a existing principal info object for that? I'm not sure about
> creating them in content space.

I think zope.app.authentication.interfaces.IPrincipalInfo should made it (not 
tried). This makes more liking that method.
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users