On Tue, Mar 01, 2011 at 01:35:46PM -0500, Tres Seaver wrote:
> > sorry for some kind of off-topic, but what's the status on repoze.who
> > 2.0? It seems a great piece of software, but why it's still in alpha
> > stage?
...
> Note that the core design, and much of the code, comes from r.who 1,
> whi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/01/2011 04:02 AM, Andrey Popp wrote:
> Hello Tres,
>
>> FWIW, repoze.who 2.0 explicitly works to enable / ease using the
>> machinery where needed in the app by exposing the configured plugins via
>> an API (the login and logout views are the o
Hello Tres,
> FWIW, repoze.who 2.0 explicitly works to enable / ease using the
> machinery where needed in the app by exposing the configured plugins via
> an API (the login and logout views are the obvious consumers). It also
> retainis the flexibility of middleware for enforcing policies.
sorr
Clearly it will take time for individuals to understand which functionality
best belongs in each layer. REMOTE_USER makes great middleware but it's
trivial to move that bit, or sessions, into or out of Pyramid as desired.
--
You received this message because you are subscribed to the Google Gro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/28/2011 09:46 AM, Daniel Holth wrote:
>> There seems to be a trend in pyramid development of re-implementing a
>> lot of what was previously done in various layers of wsgi middleware
>> ( session, auth, ...) and moving those part inside the main
On Sun, Feb 27, 2011 at 2:15 PM, oO wrote:
> Sorry if this is a basic question, but as I'm starting to add more and
> more layers of complexity to my first pyramid based applications, I'm
> starting to wonder about some of the benefits of using pyramid
> specific implementations as opposed to re-
