On Mon, 2009-02-02 at 05:57 -0800, Mike wrote: > With a modified version of Robin Dunn's fcgi.py module that adapts > fcgi to wsgi, I've set up Django to run under mod_fcgid. One good > thing about mod_fcgid is that it does all process management for you, > which makes this setup quite straightforward.
Given the multiple options that already exist for integrating Django with Apache via modules, I'm not immediately excited by the possibility of including yet another one in core. Those who use Apache already have a lot of out-of-the-box choices (and our goal is to make Django usable out of the box, not cover every single possible install option) and those who don't use Apache (which is also a large number of people) aren't going to use mod_fcgid anyway. I understand that it's possible this handler may offer some alternative options that in some situation is better or different from any existing option. But the existing options aren't bad choices and a slight variation on existing stuff isn't going to be a decider for me. However, handler modules also don't need to be part of core, since they're, ultimately, just Python functions that are called. So it should be easy to have this be a third-party option that people could download and use if they wanted to go that way. That's all just my personal opinion, but hopefully you can see the logic I'm following. Maybe Jacob or Adrian or one of the other maintainers will be really thrilled by the possibility, but it might be worth holding off creating a ticket for now, until you see if it's really worthwhile doing so. Generally, something like this would exist as a successful and indispensable third-party project before it would be considered for core. > > Also, since Robin's module works both in a cgi and fcgi context, > switching a django site between cgi and fastcgi is a one-liner Albeit a really bad idea for something like Django unless things like, say, performance are not an objective. :-( It's 2009 already. We're reasonably justified in not accommodating web servers that still require 1998-vintage installation. As soon as we do, we'd be obligated to support it -- both in code and support forums -- forever (or at least a really long time), which is an unnecessary extra burden. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
