On 7/13/09 8:21 PM, Rob Miller wrote:
there's one other thing i noticed from browsing through the code in your
links above, though... i r87732
(https://dev.plone.org/collective/changeset/87732/Products.membrane/trunk/Products/membrane/tools/membrane.py)
it looks like wichert changed the name of the membrane tool's
"getUserAuthProvider" method to "getUserObject". while i understand the
motivation there, the new name makes me a bit uneasy. it is an explicit
goal of membrane to NOT restrict people to a single content object
representing a user, and it is possible to have several different
content objects all contributing to the user object that PAS creates.
'getUserObject' obscures this, IMO, which is why the method was called
getUserAuthProvider, since that describes exactly what is being returned
w/o making any claims that the returned object represents more than that.
not a huge deal, but i think it's important enough to mention.
My renaming was on purpose: I wanted to be able to have user objects
that do not support authentication. This can be useful when you use
other methods than workflow to allow users to authenticate, for example
by using a marker interface that controls adaptability to the
authentication interface.
For that reason I refactored things so you always start with a very
minimal user object which exposes the very minimum required to work with
PAS: a user id and a login name. All other possible facets of a user
(properties, authentication, etc.) are split out into separate adapters.
That allows for maximum flexibility in building your users.
Wichert.
--
Archive:
http://www.coactivate.org/projects/remember/lists/remember/archive/2009/07/1248094093948
To unsubscribe send an email with subject "unsubscribe" to
[email protected]. Please contact [email protected] for
questions.
