<html><body>On 07:12 pm, rspringob@vmware.com wrote:<br />>I am designing a scheduling system and am wondering if twister is the right<br />>tool for the job. The typical model is to have a server answering many<br />>clients. I am looking at the inverse of having a solitary dispatcher (client)<br />>contact many different hosts (servers) in order to pass them a job.   Looking<br />>at the examples in the documentation, it looks like the normal procedure is<br />>to have one persistent connection per reactor. Am I trying to do a bad thing<br />>with twister?<br /><br />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.<br /><br /></body></html>