Part of twisted.protocols.loopback View Source View In Hierarchy
|Method||write||Write some data to the physical connection, in sequence, in a non-blocking fashion.|
|Method||writeSequence||Write a list of strings to the physical connection.|
|Method||loseConnection||Close my connection, after writing all pending data.|
|Method||getHost||Similar to getPeer, but returns an address describing this side of the connection.|
|Method||getPeer||Get the remote address of this connection.|
|Method||registerProducer||Register to receive data from a producer.|
|Method||unregisterProducer||Stop consuming data from a producer, without disconnecting.|
If possible, make sure that it is all written. No data will ever be lost, although (obviously) the connection may be closed before it all gets through.
If possible, make sure that all of the data is written to the socket at once, without first copying it all into a single string.
Note that if there is a registered producer on a transport it will not be closed until the producer has been unregistered.
Treat this method with caution. It is the unfortunate result of the CGI and Jabber standards, but should not be considered reliable for the usual host of reasons; port forwarding, proxying, firewalls, IP masquerading, etc.
This sets self to be a consumer for a producer. When this object runs out of data (as when a send(2) call on a socket succeeds in moving the last data from a userspace buffer into a kernelspace buffer), it will ask the producer to resumeProducing().
resumeProducing will be called once each time data
pauseProducing will be called whenever the write
buffer fills up and
resumeProducing will only be called when
|Raises||RuntimeError||If a producer is already registered.|