[Grok-dev] Re: WSGI, Repoze and deployment questions

Tres Seaver tseaver at palladion.com
Fri Nov 23 11:26:15 EST 2007

Hash: SHA1

Philipp von Weitershausen wrote:

> I think, as a short term goal, we should move grok and grokproject to a 
> WSGI-based sandbox, using zope.app.wsgi. I think this is what repoze 
> uses for now as well, for the lack of a better way to integrate Zope 3 
> and WSGI. That's not to say zope.app.wsgi is a particularly bad way, 
> though it is a bit monolithic. It still allows you to deploy anywhere 
> you'd like (including mod_wsgi) and plug in various middlewares which I 
> have in almost all of my projects (e.g. Deliverance, custom sessioning 
> middleware, debugging middleware during development, etc.)
> A long-term goal could be to go repoze way and "explode" the Zope 3 
> publisher, much like they did for Zope 2. Because then we can use one 
> transaction middlware across Zope 2, Zope 3 and possibly other systems, 
> and one exception formatter, etc. without carrying the baggage imposed 
> by Zope 3 (which is all Component Architecture driven rather than 
> WSGI-driven).

We intend to do this explosion for the Zope3 publisher, but it hasn't
gotten to the top of the prioitiy list, due largely to two factors:

 - the monolithic version works;

 - the guts of the monolithic version are about as obfuscated
   as anything in Zope3 (a funky priority-based registry for
   request-publication-factory-factories?  You've got to be
   kidding me!)

- --
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


More information about the Grok-dev mailing list