On the contrary, the auth demo is actually very good and was
instrumental in allowing me understand the basic mechanisms.
The problem I encountered was that it was a bit simple and I was unable
to go easily from the demo to implementing a hierarchical permissions
system and learn about the role of traversal resources in generating
contexts with dynamic __acl__ properties.
I understand that that is not strictly required but now that I sort of
get it, traversal based acl generation seems to be the simplest way to
get to complex auth(n/z) schemes.
AM
On 09/13/2013 01:45 PM, Michael Merickel wrote:
On Fri, Sep 13, 2013 at 3:28 PM, AM <[email protected]
<mailto:[email protected]>> wrote:
@mmrickels auth demo is helpful but I felt that I had to read the
traversal docs and examples about 5 times before I was able to map
the demo and docs to actual things that I wanted to do.
Can you highlight any parts of the auth demo that were particularly
confounding? I need to revisit that thing at some point. If you don't
want to hijack the thread just open an issue
https://github.com/mmerickel/pyramid_auth_demo/issues.
--
You received this message because you are subscribed to the Google
Groups "pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/groups/opt_out.
