> On Dec 31, 2011 4:41 PM, "John Anderson" <[email protected] > <mailto:[email protected]>> wrote: > > So what is the reasoning behind needing a production ready webserver > included with the framework by default? Couldn't we just include > something lightweight that works for development and allow people to > make their own decision on what webserver they would like to use? > On 12/31/2011 04:51 PM, Michael Merickel wrote: > > I think the goal is something that won't just fold over in production. > wsgiref is single threaded and in just no way capable of being > deployed. This way if someone deploys it without knowing any better > they at least have a chance. >
I think what would match up more with pyramid's goals as a foundation for building frameworks, being minimal, and not making decisions for the developers would be to not ship a server at all and part of the documentation would be how to choose the webserver that is right for them. Similar to how they have to choose a template engine, orm, form library, etc. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
