well, it does not necessarily correspond, but from what I see on tcpdump with
loopback device and on LAN (with TCP NoDelay set), it practically works.
the problem with your suggestion: I want to test the other end .. and that is
not Twisted (its i.e. Firefox .. the protocol to test is WebSockets)
On 11.08.11 23:13, "Christopher Armstrong" <ra...@twistedmatrix.com> wrote:
On Thu, Aug 11, 2011 at 5:06 PM, Tobias Oberstein <tobias.oberst...@tavendo.de>
wrote:
For testing implementations of a TCP-based protocol, I am testing
if an implementation is agnostic wrt to in what chops in receives
octets from the wire ("stream clean").
To do that, I force out octets from the protocol test driver (written
in Twisted) in differently sized chops, down to single octets.
While this is a noble goal, your method isn't really right: in TCP, the chunks
you write on one end do not correspond to the chunks you receive on the other
end after they've gone through a TCP stack and network. The best way to verify
that your client is stream clean is to write unit tests that explicitly call
its dataReceived method with different-sized chunks.
--
Christopher Armstrong
http://radix.twistedmatrix.com/
http://planet-if.com/
_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
