Re: [openstack-dev] [api][all] - Openstack.error common library

2015-03-03 Thread Everett Toews
On Feb 25, 2015, at 10:47 AM, Doug Hellmann d...@doughellmann.commailto: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

Re: [openstack-dev] [api][all] - Openstack.error common library

2015-02-27 Thread Eugeniya Kudryashova
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 already

Re: [openstack-dev] [api][all] - Openstack.error common library

2015-02-26 Thread Dolph Mathews
On Wed, Feb 25, 2015 at 10:47 AM, Doug Hellmann 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

Re: [openstack-dev] [api][all] - Openstack.error common library

2015-02-25 Thread Doug Hellmann
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 collect all