soon as possible, rather than waiting for the next write.

code out into separate classes.

vulnerable to traffic analysis can frame their data independently of
packet boundaries.

predefined tags in the protocol and serial components, and "IV" for
the encrypted IVs used to identify connections in the transport
component.

authenticate each frame before parsing its contents. Each connection
starts with a tag, followed by any number of frames, each starting
with the frame number (32 bits) and payload length (16 bits), and
ending with a MAC (256 bits).

Tags have the following format: 32 bits reserved, 16 bits for the
transport ID, 32 bits for the connection number, 32 bits (set to zero
in the tag) for the frame number, and 16 bits (set to zero in the tag)
for the block number. The tag is encrypted with the tag key in
ECB mode.

Frame numbers for each connection must start from zero and must be
contiguous and strictly increasing. Each frame is encrypted with the
frame key in CTR mode, using the plaintext tag with the appropriate
frame number to initialise the counter.

The maximum frame size is 64 KiB, including header and footer. The
maximum amount of data that can be sent over a connection is 2^32
frames - roughly 2^48 bytes, or 8 terabytes, with the maximum frame
size of 64 KiB. If that isn't sufficient we can add another 16 bits to
the frame counter.

transport format.

table so it's not necessary to hold a write lock on the (heavily used)
contacts table to update them.

writer - this will allow it to be saved so new connections can work
out whether they should send updates.

delimited form.

it responds.

allow writers to starve. If this test passes on Java 5 and 6, we can
get rid of SynchronizedDatabaseComponent and merge
ReadWriteLockDatabaseComponent with DatabaseComponentImpl.

from PacketReader (which belongs in the transport component).

encrypting and decrypting packets. Moved the test to the main package
since it's an integration test for several components.

protocol component to Protocol{Reader,Writer}Factory.

fact that the cipher wants to operate a block at a time even though
it's in CTR mode.

by the code that recognises tags. Implemented ConnectionRecogniser
(untested).

encrypted secrets retrieved from the database.

encryption keys from them (untested).

responsible for wrapping/unwrapping them).

getConnectionWindow() and setConnectionWindow() through the
DatabaseComponent interface.

window.

window sliding (untested).