On Fri, Dec 19, 2008 at 7:46 PM, Graham Dumpleton
<[email protected]> wrote:
>
> Finally found some time to blog about some stuff.
>
> http://blog.dscpl.com.au/2008/12/using-modwsgi-when-developing-django.html
>
> This just highlights some stuff which was already in documentation,
> but tend to find that people don't read deep enough to realise this is
> possible and was getting a bit tired of comments on Django forums and
> irc channels saying mod_wsgi couldn't do this. :-)

FWIW most of the naysayers have probably never deployed Django on
mod_wsgi because:

a.) they are too lazy/under too much time pressure to read detailed
documentation on the wiki and just wanted something they could copy
and paste into a terminal. Or;

b.) they are too lazy/under too much time pressure to search the
mod_wsgi mailing list.

A lot of "sysadmins" these days are pretty much the ADHD
trial-and-error types who expect to find "working examples" that they
can simply copy and paste and modify to suit their needs. Since they
forgo reading the documentation *before* diving into a complex
configuration where a lot can go wrong, they are left with the
impression that mod_wsgi is inadequate for their requirements.

Oh, and I blame PHP :-)
-- 
Best Regards,
Nimrod A. Abing

W http://arsenic.ph/
W http://preownedcar.com/
W http://preownedbike.com/
W http://abing.gotdns.com/

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

Reply via email to