Kevin Dangoor wrote: > On 1/30/06, Bob Ippolito <[EMAIL PROTECTED]> wrote: > > This seems like a much simpler and more robust platform to build on > > top of. It'd probably help out with performance too, since it > > doesn't have all of that filter crap on every hit (which belongs in > > middleware or decorators anyway, not per-object). I'd trade the > > advantages of WSGI for the "stability"/ancestry of CherryPy any day, > > but I'm not Kevin :)
Hopefully filter dispatching will be improved in the future. > That may be, but you *are* Bob. I tend to pay attention to your > opinions, because they're often pretty close to the mark. > > As an aside to this, Christian *dowski has put forth a minor update to > the CP server that allows use of WSGI middleware with CherryPy: > http://projects.dowski.com/projects/cp_middleware_server I am hoping that this will be adopted into the CP core. Here is the open ticket with a patch and and example that uses EvalException and Allan Saddi's session middleware. http://www.cherrypy.org/ticket/455 If it is not included in the CP core, I will release it separately. This can be used in conjunction with my wsgi_filter module so that CP can dispatch to other wsgi applications. http://projects.dowski.com/projects/wsgi_filter Incidentally, WSGI filter should work with stock CP 2.2beta. Christian Wyglendowski (not *dowski ;-) http://www.dowski.com
