Commits on Sep 25, 2011
Previously, when the receiver got a duplicate start packet, it created a new connection object, and since we keep track of connections by the IP address and port tuple, it mistakenly erased the state it had for a connection, causing incorrect acks to be sent. This fix causes the sender to never create a new connection objects for an (IP,port) for which we have an active connection.shaddi committed
Sep 25, 2011
Commits on Sep 23, 2011
Commits on Sep 19, 2011
Commits on Sep 14, 2011
Commits on Sep 3, 2011
- Receiver now times out a connection after a specified amount of time - Fixed some command line parameters - Receiver would get confused by re-ordered packets, fixed this
This reverts commit 7aacf25.
…convenience method"" This reverts commit 494055f.
…nce method" This reverts commit c42116f.
- BasicSender.make_packet() now takes msg as an optional parameter - Added connection state to receiver. - Added "end-ack" message type to receiver and senders (three-way terminal handshake) Rather than terminating a connection on an "end" packet, the receiver now waits for an end-ack packet, which MUST arrive while the connection is already in the "end" connection state (meaning all data up to an "end" packet has been received in-order). - Since the sender may quit immediately after sending the end-ack, we can leave the sender in an inconsistent state; we need to add a per-connection timeout to end connections for which we never receive the end-ack. This is not implemented. Note, this is untested: supper time.
Commits on Aug 25, 2011
Commits on Aug 24, 2011
Commits on Aug 17, 2011