Hi,
I was able to reproduce http://www.zope.org/Collectors/Zope3-dev/714 today.
We have a patch from the reporter without and I don't see why the
current tests fail to catch this behavior in the first place.
Did we ever drop support for ZServer? The changelog reads 'replaced
ZServer with
Christian Theune wrote:
Hi,
I was able to reproduce http://www.zope.org/Collectors/Zope3-dev/714 today.
We have a patch from the reporter without and I don't see why the
current tests fail to catch this behavior in the first place.
Did we ever drop support for ZServer? The changelog reads
Stephan Richter wrote:
On Tuesday 19 December 2006 08:24, Jim Fulton wrote:
Here is what I'd like to see. I'd like to see someone get more involved
in the WSGI effort. A very specific thing I think is needed is a WSGI
server benchmark that can be used to evaluate different WSGI servers for
Anyone played with Nuxeo's 'funkload'? That's probably one of the most
interesting stress/benchmark tools out there. There are other
non-Python options too, like 'JMeter' (I believe that's the name) and
Microsoft Web Capacity Analisys Tool (free download I believe).
--
Sidnei da Silva
Enfold
Christian Theune wrote at 2006-12-19 10:06 +0100:
...
Did we ever drop support for ZServer? The changelog reads 'replaced
ZServer with twisted' which sounds very much like ZServer was defined
obsolete.
I have understood the discussions differently:
As I understood ZServer should stay
