> Overall, for real world dynamic Python applications the performance > differences between different web hosting mechanisms are going to be > very little. So, since all can be made to work, you are generally > better off just choosing that solution which fits your mind set and > which you find to be easy to install, configure and maintain. Issues > such as stability and quality of documentation and ongoing support > should also be considered for critical production systems.
The only exception to this is when you make extensive use of features of the webserver. The example that comes to mind immediately is the nginx-memcached plugin which serves rendered pages up out of memcache directly. If your application can work with this world view, you can get really significant performance benefits by effectively cutting your app code entirely out of the request/response and just letting the web server do it. But at that point the web server is effectively a part of your application stack, and not just a WSGI server ;) --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
