Stef dijo:

are you writing tests for SqueakNet? Because this is a cool project and with tests we could really build on top of it.

Hi Stef!

The truth is that Luciano is doing all the work in NetSqueak. And yes, he's doing lots of tests (lots and interesting). Let me copy here he's last commit log to http://www.squeaksource.com/Net.html. For every thing he does, he does tests. The last thing he implemented for testing is the RealisticLoopback InternalNetworkDevice. A subclass of Loopback which implements drops, corruption and delays. To test how the stack behaves in this cases. On the other side, for SqueakNOS I'm not writing no tests. I don't really know how to write tests for the HardwareDevices, but the truth is that I have not yet felt the magic of tests, so I'm not pushing it too hard... mea culpa.

ok, the commit log for your pleasure:

Name: Net-len.13 Author: len Time: 1 August 2006, 2:02:21 pm UUID: dcfbc174-bcdb-4690-8af7-b46ab4704681 Ancestors: Net-len.12

- Implemented delayed ACKs in TCP. - New tests for TCP. - Timers now are working. - Refactored InterfaceConduit/ProtocolStack... the two of them are now one: NetInterface. I don't know yet if this is good enough, but I had to do this change because I needed to start and stop timers (TCP, IP reassembly and ARP timers), and the same object that understands #up and #down (the interface) and manages the process that handles incomming packets seems to be the right object to start and stop timers. All processes that are required for the networking stack are started and stopped sending #up and #down to the network interface.