Reset method needs to zero out buffer list bytes.
Add reconnect method to TCP socket.
Remove SSL Logging. Adhere to modified DNSQueryClient interface.
Fix comments.
Better logging in the case of an unhandled exception in main Selector event loop.
Add new properties hash attribute to SlaveRegistration message.
Allow log directory override via command line parameter.
Get checkpoint directory and FS from new ContentPath variable.
Support https via http queue.
Adhere to modified DNSQueryClient interface.
Extract checkpoint path via contentDataDir property and store JSON properties hash from master sync message.
Release old memory prioir to reload of bloom filter data.
Add additional command line parameters to support separate Segment and Content (Checkpoint) data directories.
Reabstract resolver interface and base classes.
Implement Async DNS Resolver.
Preliminary UDP interface implementation.
Pass in HTTP Connection object in downloader callback. Add calling thread awareness in shutdown method.

Don't wait if caller is in Downloader's Event Thread. Ensure repetetive
calls to shutdown don't cause NPEs.
Add timeout support to S3InputStream.

S3InputStream will stop pulling data from S3 if the consumer thread is
not pulling data fast enough to keep buffered data below a certain
threhsold. Unfortunately S3 is very aggressive about terminating the
connection if the receiver is not pulling data fast enough. A timer
(running in the S3Downloader's Event Thread) is used to detect stall
conditions. Once such a condition is detected, the consumer thread is
awoken from its WAIT state and allowed to reinitiate the S3 request
(using a RANGED http GET).
Cleanup part resources.

Release memory once we have received an ack from S3 for a part upload.
Use S3MultipartUploadStream in S3NFileSystem.

Use new S3MultipartUploadStream as the underlying OutputStream for our
version of the S3N FileSystem. S3MultipartUploadStream uses the Amazon
multi-part protocol, and ,thus, does not need to pre-buffer the file to
the local FS (like the original S3NFileSystem Impl) before initiating a
transfer up to S3. Also, S3MultipartUploadStream is more resilient to
failures (thanks to its use of the multi-part protocol).