Randy,
Thanks for the detailed list; this really puts into perspective what
the important considerations are for getting PyISAPIe to be more
flexible with Django.
For now, I think I'll try to figure out why having multiple instances
of PyISAPIe in the same application pool causes trouble. Are the
worker processes just crashing on you when you request a page?
- Phillip
On May 10, 1:52 pm, Randy Syring <
ra...@rcs-comp.com> wrote:
> Hi again,
>
> Ok, my goals are as follows, with the goals at the top being the more
> important/most efficient ones (at least IMO):
>
> 1. Run multiple instances of Django on the same IIS server with only
> one instance of PyISAPIe.dll. This would allow a system admin to
> setup PyISAPIe once and let non-admin users configure their python
> setup by using a specially named file in the root of the virtual
> directory or website.
> * Problem: os.environ['DJANGO_SETTINGS_MODULE'] is required to
> get Django running correctly. However, this value is set at
> the application level. Therefore, even if that value is set
> multiple times by Http.Isapi (the PyISAPIe script), Django
> only cares about the first instance. It is therefore
> currently impossible, as best I understand, to run multiple
> instances of Django under the same PyISAPIe.dll instance.
> 2. Run multiple instances of Django on the same IIS server with
> multiple instances of PyISAPIe.dll on IIS 5.1 or IIS 6 (without
> multiple application pools). This still requires admin
> intervention for every website installed, but would allow
> development testing on Windows XP with virtual directories and
> would require less resources on IIS.
> 1. Problem 1: when configuring IIS 5.1 in the same setup as
> noted below using virtual directories, the second
> application to be initiated doesn't work.
> 2. Problem 2: when configuring IIS 6.0 in the same setup as
> noted below using websites that share an application pool,
> the system becomes unstable
> 3. Run multiple instances of Django on the same IIS server
> (completed). It requires a website or virtual directory for each
> django instances.
> * Each website or virtual directory will need to have its own
> PyISAPIe.dll and HTTP folder
> * my directory structure is as follows
> o c:\websites\django1
> + pyisapi
> # PyISAPIe.dll
> # HTTP (directory with HTTP files)
> + python
> # djtutorial1 (django project directory)
> + wwwroot
> o c:\websites\django2
> + pyisapi
> # PyISAPIe.dll
> # HTTP (directory with HTTP files)
> + python
> # djtutorial2 (django project directory)
> + wwwroot
> * my websites are as follows
> o
django1.example.com
> + home directory is c:\websites\django1
> + Has its own application pool named django1 (this
> is required, if you try to run multiples
> instances of PyISAPIe in the same application
> pool the system becomes unstable and stops working)
> o
django2.example.com
> + home directory is c:\websites\django2
> + Has its own application pool named django2
>
> Ok, so the third goal has been accomplished as far as I can tell. I was
> initially concerned that having multiple application pools might consume
> more resources than is necessary, bit it probably isn't an issue based
> on this comment:
>
> Each application pool will consume resources, so i suppose that is the
> disadvantage. You should however compare this to the advantages of
> application pools.
> 10 application pools on a server is however not in any way overkill.
> One
> application pool per website is not strange at all, instead it is a
> quite
> good configuration (of course this depends on the website(s) and its
> web
> applications).
> You have too many application pools when the server is running short on
> resources because the application pools consume too much resources.
> --
> Regards,
> Kristofer Gafvert (IIS MVP)
>
> found here:
>
http://www.eggheadcafe.com/forumarchives/inetserveriis/Nov2005/post24...
>
> However, I would still like to see the other two goals accomplished.
> Goal #1 probably doesn't have anything to do with PyISAPIe as far as I
> can tell. That is probably a Django issue which I have asked about here:
>
>
http://groups.google.com/group/django-developers/browse_thread/thread...
>
> The second goal, however, may be a PyISAPIe goal. Would it possible to
> run multiple instances if PyISAPIe in the same application pool? This
> would use less resources on IIS 6 and enable IIS 5.1 to have multiple
> Django applications using virtual directories.
>
> Thoughts, comments, questions welcome.
>
> Thanks.
>
> --
> --------------------------------------
> Randy Syring
> RCS Computers & Web Solutions
>
502-644-4776http://www.rcs-comp.com