On Sat, 21 Nov 2009 11:02:41 +0100 Markus Armbruster <arm...@redhat.com> wrote:
> Now, what should a client do when it discovers the monitor command it > needs to use has grown a new error? Refuse to use the command for fear > of having to present a sub-par error message to the user in case it > fails? What's your solution for this problem? > Yes, the client needs updating in such a scenario. But since it's a > normal, expected situation, I wouldn't call it a client bug. And > regardless how we call it, we better handle it gracefully. The best thing the client can do here is to print the error class.
