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. :-)
Graham, it would also be worth noting that this approach has some caveats. This would be fine if you are only touching 1 or 2 files in your app. But there is the possibility that auto-reload will mess up things in a larger deployment. For instance, take a large Django-based deployment. You post updates to the app via FTP, which usually sends up one file at a time (I know you can do parallel transfers, but I use sitecopy and some servers have limits on concurrent connections). You are ordered to make changes across several files in the app. Now, some of changes in some of the files are dependent on changes found in other files. When you upload these changes, users might experience internal server errors as the partial update is progressing because server reloads files which have dependencies on files which have not yet been uploaded. -- 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 -~----------~----~----~----~------~----~------~--~---
