[Zope3-dev] Satellites and Launchpad
When starting to implement the ReusableAction feature, I noticed that we're not using launchpad correctly now. I'm not sure what else we do wrong, so I started a proposal on what we need to do to start using launchpad right again. See http://wiki.zope.org/zope3/SatellitesAndLaunchpad Christian ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Proposal: Make zope.configuration actions better re-usable
As this didn't spur any resistance, I'll be implementing this now. I'll make a b1 release of zope.configuration and move the trunk of zope.configuration to 3.5 after that, my changes will go to a working-branch first. Christian Am Dienstag, den 10.07.2007, 16:06 -0400 schrieb Fred Drake: On 7/10/07, Marius Gedminas [EMAIL PROTECTED] wrote: in addition to emitting a deprecation warning, perhaps? There's no need to deprecate action(), and I suspect no value in doing so, either. -Fred ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] How to debug zope3 if it completely hangs?
Fabio Tranchitella wrote: I'd like to know if zserver is a good choice for high loads or if it deprecated and I should stay with twisted. We run some pretty high load apps, and we're happy with zserver. Was zserver disabled only for security reasons? I don't believe it had anything to do with security. -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: How to debug zope3 if it completely hangs?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Benji York wrote: Fabio Tranchitella wrote: I'd like to know if zserver is a good choice for high loads or if it deprecated and I should stay with twisted. We run some pretty high load apps, and we're happy with zserver. Was zserver disabled only for security reasons? I don't believe it had anything to do with security. Nope: it was disabled because: - Not many people feel competent to extend ZServer. - People thought that using a server maintained by others was better than maintaining one ourselves. - Twisted offers potential features which seemed interesting at the time (I don't know how many of them actually got integrated). I prefer ZServer becuase: - It is faster. - It is less complex. - It got *lots* of attention for real-world scaling issues, and is rock-solid stable. - I don't need the extra shiny features. Note that the flavor-of-the-month is actually WSGI now, rather than Tsisted (which uses the WSGI support): see Philipp's zope on a paste demo, for instance. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGlkLn+gerLs4ltQ4RAog7AKCwL1HTkA5jTyaRH8KnRO0zctRyEACgqDtE WJp8yaqXzRFAf/hf6O1HNmI= =4ony -END PGP SIGNATURE- ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: How to debug zope3 if it completely hangs?
On Jul 12, 2007, at 11:04 AM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Benji York wrote: Fabio Tranchitella wrote: I'd like to know if zserver is a good choice for high loads or if it deprecated and I should stay with twisted. We run some pretty high load apps, and we're happy with zserver. Was zserver disabled only for security reasons? I don't believe it had anything to do with security. Nope: it was disabled because: Actually, Zope 3 doesn't use ZServer. Never has. It uses zope.server which is a different implementation. It was made to be no-longer the default server. This was a mistake BTW. My bad. zope.server is still supported. - Not many people feel competent to extend ZServer. - People thought that using a server maintained by others was better than maintaining one ourselves. Yup. ... I prefer ZServer becuase: - It is faster. We (ZC) have had serious problems with the twisted server in production. We no-longer use it. It may have improved. It's worth noting that the trouble we've had might be due to something we/I did in the integration. :( Chasing this is not a priority of mine. - It is less complex. I'm not so sure about this. Maybe. - It got *lots* of attention for real-world scaling issues, and is rock-solid stable. I don't think this is true, or at least not as true as you think it is. :) The zope.server != ZServer. :( It seems to be working reasonably well, but it is not the same server that has served Zope 2 well for many years. Not counting Twisted, we are currently supporting 2 servers, ZServer and zserver. :( ... Note that the flavor-of-the-month is actually WSGI now, rather than Tsisted (which uses the WSGI support): see Philipp's zope on a paste demo, for instance. I really wish someone would create some server benchmarks for WSGI so that we could have a more rational basis for evaluationg servers. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
