We should proceed by getting Z2 and Z3 to use a common
publisher, presumingly based on the Z3 publisher.  This common
publisher should:

- Be well documented and tested.

- Use WSGI for HTTP

- Be backward compatible with Both Z2 and Z3

- Should be highly customizable through components.  This will
  hopefully allow z2-stype and z3-style publication to coexist in
  a single app server.

Again, I expect that the Z3 publisher will be the best starting point.

Note that the Z3 publication framework splits functionality
currently provided by the Z2 publisher into a publisher and a
publication object.  An initial step might be top come up with
a Z2 publication object that works with the Z3 publisher.


Sidnei da Silva wrote:
On Tue, Dec 06, 2005 at 07:56:00PM -0500, Jim Fulton wrote:
| Sidnei da Silva wrote:
| >Best I can tell, it should be pretty doable no?
| | The key is to move to WSGI. Zope 3's publisher now uses
| WSGI and so does twisted. For HTTP, the Zope 3 pubisher isn't
| based on twisted, it is based on WSGI.  There is twisted-specific
| glue for FTP.

So, if I'm understanding this correctly, we need to turn the Z2
publisher into a WSGI app that can be used with the twisted server?

Should a version of the Z2 ZServer that supports WSGI apps exist?

| The most important project here, IMO, is to rewire Zope 2
| to use the Zope 3 publisher.  And, of course, to update the
| Zope 3 publisher with features from the Zope 2 publisher that
| are missing from the Zope 3 publisher (e.g. streaming).

Yes, this is very important.

Jim Fulton           mailto:[EMAIL PROTECTED]       Python Powered!
CTO                  (540) 361-1714            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org
Zope3-dev mailing list
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to