On 07:12 pm, rspringob@vmware.com wrote:

I am designing a scheduling system and am wondering if twister is the right tool for the job. The typical model is to have a server answering many clients. I am looking at the inverse of having a solitary dispatcher (client) contact many different hosts (servers) in order to pass them a job. Looking at the examples in the documentation, it looks like the normal procedure is to have one persistent connection per reactor. Am I trying to do a bad thing with twister?

No, Twiste*d* lets you use multiple connections with the same reactor; in fact, you can only have one reactor instance in your program. The reactor is an event loop; it handles many event sources at once.