Skip to content Skip to sidebar Skip to footer

Twisted Framework Server Making Connections As A Client?

So first off, let me show you my code and the error it returns: print 'before import' from twisted.internet import protocol # imports print 'after protocol' from twisted.internet

Solution 1:

On UNIX, Twisted sets up a thread-waker file descriptor using a pipe. However, on Windows, anonymous pipes have several implementation issues and discrepancies between different Windows versions, so it uses a socket pair. Creating this socket pair involves connecting back to localhost, so, certain overly-aggressive firewall configurations can trigger this area.


Post a Comment for "Twisted Framework Server Making Connections As A Client?"