On Feb 25, 2015, at 10:47 AM, Doug Hellmann
mailto:d...@doughellmann.com>> wrote:
On Wed, Feb 25, 2015, at 09:33 AM, Eugeniya Kudryashova wrote:
Hi, stackers!
As was suggested in topic [1], using an HTTP header was a good solution
for
communicating common/standardized OpenStack API error codes.
Thanks for the replies!
> Could you elaborate bit what you want to have in the headers and why? Our
plan has been so > far having the error code in the message payload so that
it?s easily available for users and
> operators. What this library you?re proposing would be actually doing?
I’ve alrea
On Wed, Feb 25, 2015 at 10:47 AM, Doug Hellmann
wrote:
>
>
> On Wed, Feb 25, 2015, at 09:33 AM, Eugeniya Kudryashova wrote:
> > Hi, stackers!
> >
> > As was suggested in topic [1], using an HTTP header was a good solution
> > for
> > communicating common/standardized OpenStack API error codes.
>
On Wed, Feb 25, 2015, at 09:33 AM, Eugeniya Kudryashova wrote:
> Hi, stackers!
>
> As was suggested in topic [1], using an HTTP header was a good solution
> for
> communicating common/standardized OpenStack API error codes.
>
> So I’d like to begin working on a common library, which will collec
