Core Python Programming (2nd Edition)

calling the write() method of the transport object to send another message to the server,
loseConnection() is executed, closing the socket. When this occurs, the factory's clientConnection-Lost
() method will be called, and our reactor is stopped, completing execution of our script. We also stop
the reactor if a clientConnection-Failed() for some other reason.
The final part of the script is where we create a client factory and make a connection to the server and
run the reactor. Note that we instantiate the client factory here instead of passing it in to the reactor like
in the server. This is because we are not the server waiting for clients to talk to us, and its factory
makes a new protocol object for each connection. We are one client, so we make a single protocol object
that connects to the server whose factory makes one to talk to ours.
16.5.3. Executing Our TCP Server and Client(s)
The Twisted client displays output similar to all our other clients:
$ tsTclntTW.py
> Where is hope
...sending Where is hope...
[Tue Apr 18 23:53:09 2006] Where is hope
> When words fail
...sending When words fail...
[Tue Apr 18 23:53:14 2006] When words fail
>
$
The server is back to a single connection. Twisted maintains the connection and does not close the
transport after every message:
$ tsTservTW.py
waiting for connection...
...connected from: 127.0.0.1
The "connection from" output does not have the other information because we only asked for the host/
address from the getPeer() method of the server's transport object.