Alternately we could throw user errors from send. These you wouldn't need
to catch because they should not happen (and if they do it is a bug, not
something you should really catch and handle). The only concern here is
that we have to be very careful to ensure we categorize each exception

Thought about this. If I was a user of this API, I would prefer this
So you still don't have to wrap the send with try catch since those
are not meant to be caught.

On Thu, Feb 13, 2014 at 8:34 AM, Jay Kreps <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB