Hi Martijn. Many thanks for your reply. I was not aware of your project so it is quite nice to see. I am hoping to try it out. :-)

At zope's startup, a multiservice is started that currently adds the servers setup in the zope.conf. I have created configuration for additional clients and servers to use the existing thread pool and currently adding them to the multiservice using a modified main.py By having access to the multiservice object, you have complete control of each service in the app as well as the ability to incorporate other services to an already running reactor. Interaction within the app using multiple reactors is not safe - so access to this object allows you to add, remove, start or stop services.

I also want the configuration to be explicit - so to using zconfig and recipes. Overall, I am integrating apps into buildouts as well. It is useful to be explicit here too since your configuration will otherwise be in a single egg somewhere. This could make it awkward to run multiple servers performing the same task on a machine, which is the pattern I am working with.


Martijn Pieters wrote:
On 5/3/07, David Pratt <[EMAIL PROTECTED]> wrote:
Hi. I'm really wanting to do more with twisted in zope. One thing that
would make this much easier is to have a means of getting hold of the
twisted multiservice following startup as opposed to using a different
main.py (as I have been) to allow the other services to be added,
started or stopped at, or any time following startup.

I am not sure what you are looking for, but I have no trouble starting
additional services after Zope startup. See my Wing IDE integration
for Zope3, for example;


It starts additional services, such as a single-threaded HTTP debug
server on a separate port, either at Zope start or later as the user

Zope3-dev mailing list
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to