Graham Dumpleton wrote:
> On Sep 20, 8:39 am, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
> wrote:
>> On 9/19/07, Graham Dumpleton <[EMAIL PROTECTED]> wrote:
>>
>>> Not properly though.
>> Indeed -- the auth handler has always been of "works-for-me" quality;
>> I don't know nearly enough about Apache to write a proper one. I would
>> be thrilled and delighted if someone who did would step forward and
>> write something that was actually correct :)
> 
> Problem with that is it would only work with mod_python 3.3.1 as older
> versions of mod_python do not expose Apache API properly. Even then
> there are possibly still some parts of the Apache API not exposed in
> mod_python 3.3.1 which will make it harder than it needs to be.
> 
> As I flesh out the authorisation bits of mod_wsgi support, then maybe
> I'll have a brainwave and come up with something that might also work
> on mod_python (to a degree).
> 
> Are you going to be happy with something that requires mod_python
> 3.3.1?
> 
> Graham
......

I for one am not sure; are we saying that even if I'm using flup / fastcgi as 
the transport I'm not able to use that for authorization?

The real problem for me is deployment. We have multiple apps on the same 
machine. We have tried the multiple apache solution (ie a toplevel distributor 
with a secondary for the app) and found it wanting. Our preferred solution is 
fcgi as that allows us fully decoupled processes. Putting the authorization 
into 
mod_python seems to allow the possibility of cross talk even if we use separate 
interpreters. At the very least, it requires us to be aware of these issues.

I suppose this is really a problem of the apache api and I'm not familiar 
enough 
with 2.2 to know if you can get your auth requests handled via an existing 
location.
-- 
Robin Becker

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to