On Sat, 2011-12-31 at 17:01 -0600, John Anderson wrote: > > > On Dec 31, 2011 4:41 PM, "John Anderson" <[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.
I wrote the server partly so I wouldn't have to write that documentation, because keeping it in sync as the world turns is a losing battle. Not that I probably won't have to write it anyway, but, at least if I do, I'll be able to put it in the Cookbook, where it doesn't matter too much when it's immediately out of date. > Similar to how they have to choose a template engine, orm, form > library, etc. Note that only the scaffolding will depend on waitress, so I think this is consistent. Scaffolding is all about making these sorts of choices. There's really no other standalone server except wsgiref that works across the platforms we need to support, and wsgiref blows; it's totally unsuitable for any sort of production system. It'd be a special kind of hell to specialize scaffolding rendering per-platform to choose "the best" server for that platform. - C -- 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.
