Wish I saw this earlier.
I use my own cookies and auth. It was trivial to set up.
You can bootstrap any authorization/cookie setup with either an `event
subscriber` ( NewRequest ) , a `tween` that wraps your app, or by setting
up `class based View Callables` that inherit from a single base class (
which runs your setup in __init__ ).
The easiest ways I've found to handle locking down views are with
decorators:
@require_logged_in
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/groups/opt_out.
