Twisted integration (was Re: [Zope3-dev] Re: uniformly configurable request factories: bugfix or proposal?)
On Aug 5, 2005, at 6:27 AM, Stephan Richter wrote: On Thursday 04 August 2005 23:34, Tres Seaver wrote: Can you point me to the discussion of the tradeoffs involved in moving to Twisted? I have not written the proposal yet, but you can play around with the branch if you like. Then perhaps these comments should wait for the proposal, but I'll make 'em anyway. :-) I have a (perhaps unfounded) sense that its HTTP server implementation has serious scaling problems, even compared to ZServer. Not the new web2 server. Itamar and I did some very quick (non- scientific) profiling and web2 was just slightly slower than zserver. It was just a very small fraction in comparison to the time the publisher requires. ... web2 is a reimplementation from James Knight that concentrates more on the HTTP standard itself and provides a solid WSGI interface. ... Jim already convinced me to leave zserver has an alternative. Not quiet sure how I will do this, but I hope it will be as easy as switching a few options in zope.conf. ... It will not be the only way, but the default one. This looks pretty problematic to me. Going from 3.1 to 3.2, we are going to change the default publisher implementation from a proven-in- the-field publisher (arguably coming from a long line of proven-in- the-field publishers from Zope 2), to an unproven new publisher that is actually slower than the current implementation. I'm -1 on that. I am +1 on making Zope 3 WSGI-aware. I am +1 on making Twisted an optional back end. I am potentially +1 on making Twisted the default back end after we have a reasonably significant amount of concrete in- the-field experience with it. Gary ___ 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: uniformly configurable request factories: bugfix or proposal?
On Aug 4, 2005, at 11:34 PM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephan Richter wrote: On Thursday 04 August 2005 22:40, Gary Poster wrote: When trying to determine a plug point for some functionality we were contemplating, Fred Drake and I were surprised to see that zope.app.publication.httpfactory.HTTPPublicationRequestFactory allowed for specifying the SOAP request factory, but not any of the other request factories (HTTPRequest, BrowserRequest, XMLRPCRequest). This smells like an oversight/bug. I'd like to fix this for 3.1. Shrug, this is a risky change. If something goes wrong there, a lot of code will be screwed. I agree it is fairly trivial to fix, but I would prefer it to be done right. I plan to address the entire HTTPRequest/ Publication/... issue with the Twisted integration work. ... +1 for Gary's change: I don't see any risk at all, if the default remains. I agree, of course, but Stephan is release manager. Stephan, I'll try to convince you of this one more time over IRC. :-) I think it's a significant wart and oversight to have a component system that does not allow you to choose a different component for the browser request (when even another sort of request has the ability!). It should minimally go in the trunk, so if Stephan rejects it as a 3.1 bugfix then I'll write it up as a small proposal, I suppose. Gary ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
