Ticket #5392 enhancement closed fixed
Testing infrastructure for ReactorMixin tests: hooking up two protocols to each other
|Reported by:||itamar||Owned by:||itamar|
|Author:||itamar, washort||Launchpad Bug:|
I've implemented the following code a few times: run one protocol on server, another protocol connecting to it as client, run the reactor until they both disconnect and then gathering the resulting disconnect reasons. There should be utility methods for easily doing this, and at least a couple of the existing implementations should be ported to use this as a demonstration that the API is generic enough.