Getting X-FluidDB-* headers is awkward

[terrycojones]

When an API call results in an error, the FluidError instance has the FluidResponse received in args[0] and one can get at the headers from the response via err.args[0].response.headers (where err is the FluidError instance).

It would be nice if the X-FluidDB-* error headers were more easily accessible. Similarly, the request id is in err.args[0].request_id and could be promoted to more prominence in FluidError.

[ntoll]

How about simply making the references: err.headers and err.request_id..?

[terrycojones]

Here's a sample of what err.args[0].response.headers can be expected to contain for any intrepid test writer:

{
  'x-fluiddb-message': "Action 'read' not possible on category 'namespaces'.",
  'transfer-encoding': 'chunked',
  'x-fluiddb-request-id': 'API-9007-20120716-132434-468215',
  'server': 'nginx/0.7.65',
  'connection': 'keep-alive', 
  'date': 'Mon, 16 Jul 2012 13:24:34 GMT',
  'x-fluiddb-error-class': 'TBadRequest',
  'content-type': 'text/html'
}

[terrycojones]

@ntoll: sounds good!

[terrycojones]

Just using self.response = response in FluidError would make things more explicit (rather than relying on the user to know that Python exceptions have an args list).