On 4/27/06, Andreas Jung <[EMAIL PROTECTED]> wrote:
> Getting rid of ZServer is a fine goal but as long as Twisted is much slower
> (from what I've heard) ZServer has to stay (ZServer is not subject to be
> deprecated at this time).

ZServer will remain the default for now, and it will not be deprecated
unless the community wishes so. I'm guessing the community will want
to sooner or later. ;-)
Twisted is slower, but how much of a difference that makes in real
life applications I don't know. The server is in itself not a very big
performance eater in Zope. There is of course also the option to use
something else that can use WSGI, like for example zope.server, which
is much cleaner than ZServer, and probably therefore easier to

> > The risks is that somehow we introduce some subtle behavioural change
> > that isn't tested for.
> I would love to see the stuff tested with the major frameworks (CMF 2,
> Plone + CPS) before it will be merged into the trunk.


> > The traversal refactoring means that the role checking is now done
> > after each traversal step, instead of intermingled with it. The
> > functionality should be the same, but perhaps there is some untested
> > special case when it changes. We have had much larger incompatibility
> > changes in earlier major releases though.
> >
> > The WSGI refactoring may mean that somebody using internal features of
> > ZServer might need to change something. Also it means that what the
> > publish_module() method expect as parameters will change.
> >
> I have no problems with the traversal refactoring..that sound sane.

Lennart Regebro, Nuxeo     http://www.nuxeo.com/
CPS Content Management     http://www.cps-project.org/
Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists -
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to