Thanks for the tip, I've gone that route as it was the simplest to realize.
Since I had centralized all calls
to transport.write() in a wrapper in the code, I didn't had to implement an
ITransport ..
It seems to "work" (modulo the cautions you iterated) .. and I no longer use
reactor internals.
> This will always be a somewhat unreliable way to test a remote process's
> handling of packetization, since there are still two TCP/IP stacks which can
> mess around with the data in a variety of ways, but it's as good as you can do
> if you want to use normal sockets for this testing.
>
> A mor
> > I do already disable Nagle by setting TCP NoDelay.
> >
> > And I do a reactor.select(0), which sometimes breaks I guess because
> > of reactor reentry not expected, and it will break when the reactor is
> > not select() based I guess.
> >
> > So the question is: is there an alternative to react
