Thanks, but how can I pass control back to calling code after starting the reactor? Or the idea is to run it in separate thread? I understand that main idea on twisted is async processing, but this time I need to block the calling code until response is received.
On Sat, Oct 10, 2009 at 6:10 PM, Johann Borck <johann.bo...@densedata.com>wrote: > Stanislav Yudin wrote: > > Hi everyone, > > I am having a problem with current twisted trunk (rev 27375). ... So > > the problem is that the first call to execute returns from > > reactor.run() right after reactor.stop(), but second call to same > > method of same instance do not return ever. > > I believe I am doing something wrong, so please help with find out > > what I've missed. Problem code attached. > > http://twistedmatrix.com/trac/wiki/FrequentlyAskedQuestions#WhycanttheTwistedsreactorberestarted > > But since you can do everything without restarting the reactor, that's > no real limitation. > > hth, Johann > > _______________________________________________ > Twisted-Python mailing list > Twisted-Python@twistedmatrix.com > http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python >
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
