Question

I am writing a wrapper around the DefaultHttpClient to handle some of the error-prone configuration options.
For example I will pre-configure everything to handle UTF-8 properly and to shutdown the connection cleanly.

When a non-200 is returned, I thought about the client registering a handler for a specific status code and then calling it.

I would provide some default handlers to take care of simple cases.

Is this a good pattern for a clean API? If I throw exceptions, the client has to handle cases which might not happen at all as I would have to throw an exception per possible HTTP status code (or most).

The thing I like about handlers is that I can provide a couple of ‘default handlers’ which might be overwritten…

I’d like to hear your input and maybe get some more creative ideas.

Cheers

Answer 1

I wouldn’t create a different exception for each http error code. At most create one or two general exceptions and store the exact error code as part of the exception. That way if the client code just wants to log or ignore them it can, or it can get more details based on the error code.