Hi all > Betreff: Re: [Zope-dev] Zope.pipeline proposal > > Hey, > > Tres Seaver wrote: > [snip] > > In general, if you need full-on backward compatibility with the > > existing behavior of Zope2 / Zope3 / Grok, switching to a > paste-driven > > WSGI pipeline doesn't gain you much speed (but it is not a > loss, either). > > If, for a given application, you can relax the BBB > requirement, then > > some performance wins are available via WSGI which can't be made in > > the monolithic publisher (dropping out features by removing the > > middleware layer). > > As for Grok I hope we can break some backwards compatibility > and get some larger performance speedups. We definitely need > to aggressively keep moving forward in this area. Not even > primarily for speed gains but > also for comprehensibility; I find Chris's "what's it > doing" report far more worrying than differences in speed at > this point: > > http://plope.com/whatsitdoing2 > > This is why zope.pipeline is such an important effort to me. > Not that it will immediately make things better, but it would > hopefully open up a path to move the Zope Framework forward > in this area.
I absolutly agree! As far as I can see, the repoze sample doesn't open a ZODB which makes it not really comparable. Regards Roger Ineichen _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )