Add a license file.
Add some initial networking/protocol support and start broadcasting as a scheduler.
Honor option for scheduler and add a new option for specifying the
local iface to use.
Broadcast on a specific interface in the case of the scheduler.
The daemon broadcasts looking for a response, not the scheduler.
Add a message handler class that deals with tcp connections and messages
and figure out the inheritance heirarchy and relationship between node,
messagehandler, server and how the scheduler will work.  Finally, start
trying to send some tcp messages.
Setup the actual message between the scheduler and other nodes and
stop broadcasting once a node has successfully found the scheduler.
Add a third party lib named sigar that will provide machine info
about a node to the scheduler.  This lib is linked statically.
Get rid of stray project file and fixup the run scripts.
Start building and linking the sigar library correctly and begin
to use it to calculate load average.
Clean up the arguments a bit.
Provide singletons for the server and the scheduler.
Start implementing a virtual filesystem that will use fuse on linux
and mac and dokan on windows.
Turn the host info into a node info and provide scheduler information.
Actually allocate enough memory for the receiving end.
Start a skeleton for a unit test suite.
Work on the new threaded message handler and add associated test
verifying that it works.
Add a new test for passing large data through the message handler.
This reveals that we need to take care of a message coming through
in separate packets.
Take care of the message coming through in multiple packets.  This
is not correct as we copying too much data.  Makes clear that we
need a scatter/gather approach and a better method of serializing.
Rename the protocol file to message to better reflect the classes.