Hi Andrew .. I want to thank you for your help .. I just looked at the link articles that you suggested and that sounds like the correct diagnosis to the problem .. I thought that there was a solution somewhere, I was just not able to find the correct information to aid in finding out what was actually happening .. With your guidance, I think this may be the problem, I'll let you know how I fair out ..
Thanks again for your help, I had just about given up on solving this problem .. Cheers Dave W. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Andrew Bennetts Sent: Wednesday, February 24, 2010 2:01 AM To: Twisted general discussion Subject: Re: [Twisted-Python] Reactor events help request .. Watson, David wrote: [...] > However, it appears to me that the self.sendLine(msg) and or the > self.transport.write(msg) writing functions are blocked > functions waiting for a reactor event to occur at a future scheduled time > before acutally flushing out the internal write buffers .. This sounds very much like you are calling Twisted APIs from threads (other than the thread the reactor is running in). If so, that's your problem. See <http://twistedmatrix.com/trac/wiki/FrequentlyAskedQuestions#WhydoesittakealongtimefordataIsendwithtransport.writetoarriveattheothersideoftheconnection> and <http://twistedmatrix.com/documents/current/core/howto/threading.html>. -Andrew. _______________________________________________ Twisted-Python mailing list [email protected] http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python _______________________________________________ Twisted-Python mailing list [email protected] http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
