On Wednesday November 5, 2008 05:34:22 Mark Ramm wrote: > I think the key statement from the first e-mail was this: > > The simplicity of how mod_session uses HTTP_SESSION variable on input > > to application to provide session information and a response header > > for data to be stored back to the session database when request > > complete fits quite well with WSGI way of thinking and if existing > > solutions could be modified to support this way of doing things, it > > would make it really quite easy to have a WSGI application to delegate > > such responsibilities back to Apache to do it. > > This is certainly true, and I think that it should be a reasonable > task to make a repoze.who/what backend which uses this mechanism.
Yes, that would be possible with repoze.who. There may be a "mod_session" plugin which enables that functionality by means of an Identifier/Authenticator plugin. It wouldn't work with repoze.what because it runs as a repoze.who Metadata provider, and metadata providers are only called if the user has been authenticated. Cheers. -- Gustavo Narea <http://gustavonarea.net/>. Get rid of unethical constraints! Get freedomware: http://www.getgnulinux.org/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
