On Sun, Jan 11, 2009 at 3:19 PM, Tycon <[email protected]> wrote: > I guess that means routes can be taken out if I remove the routes > middleware and use my own url_for (which I was just about ready to > do). > So in your assessment a simple hello world on pylons using cherrypy > instead of paster (that is my current config) is going to be as fast > as just as an equivalent cherrypy (or pretty close, but not twice as > slow) ? >
There's a category error here. There are a few Paste-Deploy-compatible web servers. paste.httpserver and CherryPy's servers are two examples (the two most popular for Pylons users). There's also the flup servers (which aren't http), Spawning, and... some other ones I can't remember now. Whether you choose paste.httpserver or CherryPy's server is up to you, it doesn't affect any other choice. They act almost identically (CherryPy is somewhat faster, paste.httpserver has some debugging tools... maybe there's some HTTP/1.1 features that one supports that the other doesn't, but I haven't kept track). Paste Deploy is a configuration setup to glue together middleware and other components into a single http-serving-wsgi-application. It also lets you select a web server. paster serve takes the Paste Deploy configuration and actually runs it. It's kind of like an app server, but a very small app server. There's not really any runtime over head to Paste Deploy and paster serve -- they just glue things together, but by the time you are actually serving HTTP they are finished with their jobs. -- Ian Bicking | http://blog.ianbicking.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
