It seems tedious to have to mark every method that does a thrift rpc call
with "throws TException" or have to put a try-catch around every call. Why
wasn't TException made a subclass of RuntimeException? I think many RPC
implementations I've used usually make the rpc/proxy errors runtime
exceptions. There usually isn't anything you can do about it locally in the
client call anyway.

Reply via email to