Middlewares' stack order about tg2

[amol-]

environ contains the cache object before it gets pushed into the context. You will have to change the order of the middlewares by the way to make it available before the Auth.

#20 has never been tackled as since the introduction of the TGAuthMetadata it is actually pretty straightforward to use the get_user method to retrieve everything from a cache and store them in identtiy thus making the other two methods a noop

[devilicecream]

Yes, although I noticed that to change the order of the Auth and Cache middlewares is sort of painful, since the Cache middleware is attached with the add_core_middlewares method. Wouldn't be simpler to put an option in the app_cfg to allow changes in the middlewares' stack order?

Regarding #20, what you say works only with a stateful authentication. In case of a statless one, my usual approach is to validate the authentication data, making queries, in the Authenticator plugin.
Probably would be actually better to only actually make queries in the TGAuthMetadata.get_user() method as you say, but still that needs the cache manager to be created before the authentication middleware handles the request.

[devilicecream]

Also, the request environ is not actually passed to the TGAuthMetadata.get_user() method, meaning that, without a context, the only way I see to get the cache manager is to include the environ in the identity object.

[amol-]

As In TG2.3.5 most middleware have actually been moved to application wrappers this has been tackled in documentation in a way compatible with both current middleware stack and upcoming app wrappers: TurboGears/tg2docs@62140a3