On Thu, Mar 5, 2009 at 23:51, Peter Sabaini pe...@sabaini.at wrote:
Hm, the default zope.conf says twisted should be supported as an HTTP server
replacement -- is that a bug?
If it uses the word supported that is a bug, yes.
In any case, as mentioned, it does not solve your problem. But
could this be satisficed by putting an apache proxy in front of both zope
and twisted?
On Thu, Mar 5, 2009 at 6:17 AM, Peter Sabaini pe...@sabaini.at wrote:
I'd like to run a Twisted client in Zope 2.10 (for a legacy app).
How do I do that? Simply loading twisted.internet is probably not a
On Thursday 05 March 2009 18:46:33 you wrote:
could this be satisficed by putting an apache proxy in front of both zope
and twisted?
No, not really -- I'd like to use a client written on top of Twisted in a Zope
product. So, I'd need the twisted reactor and libraries running in the Python
VM
On Thu, Mar 5, 2009 at 18:59, Peter Sabaini pe...@sabaini.at wrote:
So, I'd need the twisted reactor and libraries running in the Python
VM that runs Zope. Which should be no problem except I suspect that I
shouldn't be using the (threaded) ZServer then, because I think that would
mess with
On Thursday 05 March 2009 23:33:40 you wrote:
On Thu, Mar 5, 2009 at 18:59, Peter Sabaini pe...@sabaini.at wrote:
So, I'd need the twisted reactor and libraries running in the Python
VM that runs Zope. Which should be no problem except I suspect that I
shouldn't be using the (threaded)
