2008/8/24 Nimrod A. Abing <[EMAIL PROTECTED]>: >>> Our config does not have maximum-requests specified. You do bring up a >>> very good way of dealing with scaling issues that we are anticipating. >> >> I am not sure what part of what I said is relevant to 'scaling'. In >> general when scaling is the topic, I wouldn't be using daemon mode. >> This is because when you use embedded mode you can benefit from >> Apaches ability to scale up by creating more Apache child processes to >> handle requests and then kill them off when no longer required. In >> daemon mode the number of daemon processes is fixed, so you have to >> configure number of daemon processes and threads in line with what >> maximum concurrent number of requests might realistically be. > > The plan is to use the system found in Chapter 20 of the Django book: > > http://www.djangobook.com/en/1.0/chapter20/ > > See figure 20-4 > > All the Django app servers will be running mod_wsgi and will be placed > behind a server running perlbal or Apache with mod_proxy. Looking at > our current setup, the main reason we use daemon mode is because we > needed file ownerships and permissions for uploaded files to be > handled correctly.
The problem there being that Django folks recommend mod_python. ;-) It is interesting to see in mod_wsgi site statistics that Django page is finally starting to overtake Trac page as most popular page for third party application. Rather telling though is that whereas there are lots of referrals from Trac site in its documentation to mod_wsgi site, there are hardly any coming from Django site. It just doesn't get much mention on Django site. Rather amusing is the conversations that go on on #django irc pitting mod_wsgi against mod_python. Not amusing is the lack of knowledge many of the people there appear to have about mod_wsgi and thus the information they give about mod_wsgi is rather thin, incomplete and sometimes inaccurate. Thus, although they may be recommending mod_wsgi, I fear that people when they go use it will not get the experience the others have been promising. It would be okay if people then went and read the documentation on mod_wsgi site to learn about it, but many seem not to as they often turn around and complain about the lack of documentation on mod_wsgi and how there is so much more documentation about mod_python. Sometimes one just has to shake your head and wonder why you bother. :-( > All this works with LocationMatch as well yes? Yes. And DirectoryMatch and FilesMatch. In: http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGIProcessGroup you will see the 'Context' entry being 'server config, virtual host, directory'. This tells you where in Apache configuration the directive can be used. Follow the cross link for 'Context' and you will get Apache definitions of what those mean. http://httpd.apache.org/docs/2.2/mod/directive-dict.html#Context Graham --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
