> On 6 Jan 2009, at 19:44, Mike Orr wrote: > > > - Some sites need specifically wiki features, a la MoinMoin. I've > > heard MoinMoin is difficult to set up in a WSGI environment and > > integrate into a larger site, so perhaps there's something there to > > work on. > > Some time ago I had a play with calling MoinMoin from a Pylons > controller (with a limited degree of success). MoinMoin provides a > WSGI-callable entry point, as does Trac. > > ISTM that there's a loose area pertaining to the propagation of (what > would otherwise be) application-specific user preferences to other > apps that are sharing a WSGI-based single sign-on environment, e.g. > synching user display name and email prefs across apps. It's clearly > not pertinent to the WSGI spec but it does seem rather pertinent to > apps that inhabit the WGSI layers. > > I suspect that this issue will have to be tackled by someone at some > point in the not-too-distant, as suggested by Mike's list of partially- > emerging apps. It might be nice to see the ground staked out by some > well-designed middleware. OTOH, perhaps it's more of an issue of > consensus rather than coding and hence unsuitable for a GSoC proj.
Yes, for single sign on it is more consensus on how data gets passed around. What we don't want is one specific middleware dictating how it should be done. Having a system which is also Python specific defeats the purpose. That is, if you can't use SSO mechanism across applications written in other languages, it does limit it somewhat. FWIW, I have pointed out to the TurboGears list previously how Apache 2.4 will include a mod_session family of modules which will support SSO across disparate applications, ie., PHP, Python, Perl, CGI etc etc. How information is passed around in application environment and response headers is actually quite simple. Details can be found at: http://httpd.apache.org/docs/trunk/mod/mod_session.html It would be nice if any SSO system for WSGI is compatible with that, or at least work with that. The TurboGears people have I believed already made some effort in at least supporting how mod_session from Apache will work, thus allowing the control of the SSO process to be delegated up to the Apache level, rather than it being only a solution that will work within a single WSGI application process. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
