On Aug 16, 3:40 pm, james_027 <[EMAIL PROTECTED]> wrote: > Hi, > > Ask I have successfully try to run django apps on apache/mod_python/ > winxp, I learn that apache for winxp only support worker_mpm
Actually, it only supports 'winnt' MPM, although that is effectively 'worker' with only one process. > oppose to > what django is suggesting (prefork_mpm). > > Should I worry about this? I'd simply suggest that you try it, but test your application thoroughly to ensure your application as a whole is thread safe. Whether one should use worker or prefork has been a partly contentious issue in the past, often because of me taking issue with the recommendation. What didn't make too much sense to me was that prefork was suggested over worker, yet there was never any warning that Windows couldn't be used, which is effectively worker as well. I can't find the post in the archives now, but end result of one of the discussions was that couldn't be 100 percent sure that there weren't some multithreading issues with Django, but there weren't any obvious ones known about. It is quite possible that some of the concerns about worker derived from problems with existed with multithreading in older versions of mod_python. Thus, as long as you use the latest version of mod_python and make sure any third party modules you use are also up to date, you may well have no problems. As I said though, important to make sure you test your application. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
