It could be interesting to see how TG supports such a migration and see Paste and WSGI in real life cases :)
- Sylvain Kevin Dangoor a écrit : > 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 :) > > 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 > > Something that struck me as a big gap in RhubarbTart is session > handling. Earlier today, though, Christian linked to a WSGI session > handler, so I guess there is something out there. > > Here's my philosophy on stuff like this: I aim for TurboGears to be > best-of-breed. The definition of "best-of-breed" will change over > time. (It'll also vary from person to person, but there's not much I > can do about that.) As "the best" changes, I'd like to see TurboGears > change with it. Of course, changes need to have reasonable migration > paths and all of that, which is the primary limiting factor. But, the > bigger the win, the easier it is to justify a slightly more painful > transition. > > Kevin
