On Jan 29, 2015, at 8:34 PM, Rochelle Grober
rochelle.gro...@huawei.commailto:rochelle.gro...@huawei.com wrote:
Hi folks!
Changed the tags a bit because this is a discussion for all projects and
dovetails with logging rationalization/standards/
At the Paris summit, we had a number of session
On Jan 29, 2015, at 7:34 PM, Rochelle Grober
rochelle.gro...@huawei.commailto:rochelle.gro...@huawei.com wrote:
Hi folks!
Changed the tags a bit because this is a discussion for all projects and
dovetails with logging rationalization/standards/
At the Paris summit, we had a number of session
On Jan 30, 2015, at 3:17 PM, Jesse Keating j...@bluebox.net wrote:
On 1/30/15 1:08 PM, Everett Toews wrote:
Project: A client dealing with the API already knows what project
(service) they’re dealing with. Including this in an API error message
would be redundant. That’s not necessarily so
On Fri, 2015-01-30 at 21:08 +, Everett Toews wrote:
Project: A client dealing with the API already knows what project
(service) they’re dealing with. Including this in an API error message
would be redundant. That’s not necessarily so bad and it could
actually be convenient for client
On Fri, Jan 30, 2015 at 3:08 PM, Everett Toews everett.to...@rackspace.com
wrote:
I like the idea of the log error codes being aligned with the API errors
codes but I have some thoughts/concerns.
Project: A client dealing with the API already knows what project
(service) they’re dealing
