curator-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jordan Zimmerman <jor...@jordanzimmerman.com>
Subject Re: Why do the fluent methods on the CuratorFramework throw Exception instead of InterruptedException and KeeperException
Date Fri, 20 Jun 2014 13:56:28 GMT
I considered not have declared exceptions at all. Exceptions should be “exceptional”. It’s
my belief that specific exceptions don’t add value and make coding harder. ZooKeeper has
“recoverable” exceptions which is unfortunate. Curator tries to manage the recoverable
exceptions as much as possible so when a Curator method throws an exception something wrong
is really happening.

-Jordan


From: Corey Nolet cjnolet@gmail.com
Reply: user@curator.apache.org user@curator.apache.org
Date: June 20, 2014 at 8:43:12 AM
To: user user@curator.apache.org
Subject:  Why do the fluent methods on the CuratorFramework throw Exception instead of InterruptedException
and KeeperException  

Just curious. Was there a reason for that?
Mime
View raw message