removed test for LAPACK 3.1/3.2 which makes 3.3 look like 3.2; assume that we always have at least 3.2 in this day and age.  This allows a lot more to be parallelized.
fixed GCC warning
handle send failures when the destination service is not available
removed useless callback from "startSync" parameters
numMessagesOutstanding_ must be decreased whenever a send operation fails
add support for writing to a local file as well which is deleted when the s3 file is closed
updated launcher to generate launch script
added the ability to pass arguments to a vows coffee test (useful for -m single_test)
fixed launcher script generation
Sending on an unconnected zmq socket will now drop the message.

The rational is that if the message is important then an extra
acknowledgement mechanism should be added on top to ensure that
message was properly received. This also fixes several issues where a
user would call connect but the service is not available.

Note that yes this is starting to look like we're re-implementing tcp
but it's necessary to handle the complexity of the zookeeper discovery
mechanism.
ZmqMultipleNamedClientBusProxy should no longer call the connection handler when the service is unavailable.

Turns out that this is pretty complicated to get right because we
can't call the handler while the lock is held which mean that the
naive forwarding implementation won't work. Instead we need a custom
functor to act as the callback which handles a lock-free state machine
whose behaviour changes depending on whether we're in the locked
section or not.

Note that we should eventually try to simply remove the lock by
funnelling all events (zmq and connect calls) through message loop.
added first implementation of value description functionality
Update README.md

Put in explicit license.
Create README.md
various updates of types to allow for generic value descriptions
added .gitignore
added structured JSON parsing
Added specific exception for bucket already registered
PortRangeService is now part of the ServiceProxies which can now be configured through a bootstrap.json file.

The bootstrap.json file can be specified by:
- Defining the RTBKIT_BOOTSTRAP environment variable
- Placing it in the current working directory
- Calling ServiceProxy::bootstrap with the file path

This file can configure all or any of the components of ServiceProxy
and simplifies the initialization of a service by simply making it
completely optional to initialization a ServiceProxy object when
creating a service.
fixed single inclusion guard