Is there any interest on the developers part of getting Django to
accept request parameters through the WSGI handler that, if found,
would override any settings in the main environment on a per-request
basis?
This was wrote about in another thread and would help me greatly in
getting Django to run well on IIS:
>> but
>> there are 5 django applications (5 virtual hosts defined) running
>> under this configuration. I've set this this way that every vitual
>> host uses same process group:
>> WSGIProcessGroup procgroup
> I've also tried to set same Application group for virtual hosts but
> this caused my apps to share settings and was unusable.
>That is a limitation of Django, in as much as it relies on global variables, staring with DJANGO_SETTINGS_MODULE in os.environ.
>Good WSGI applications have configuration data come in through the
>WSGI request environment. This means that it can be set on a per
>request basis, making it somewhat practical to start having the
>concept of hosting multiple instances of an application within same
>Python interpreter context. The best example of an application able to
>do this is Trac.
>The benefit of being able to do this is that the different instances
>can share the same common Python modules and it is necessary to be
>loading multiple copies in different Python interpreter instances
>within the same process as you have happening now.
reference:
http://groups.google.com/group/django-users/msg/a599553a18c92a4f