Jan Damborsky wrote: > Hi Evan, > > > Evan Layton wrote: >> This is the first draft of the Caiman Unified Design (CUD) Error >> handling service. This is intended to be generic and usable by >> the various components of CUD. This document does not contain the >> design for the logging service as that will be a separate document. >> >> We plan to spend a bit of time talking about this at the Tuesday >> meeting. > > as I will not be able to attend the meeting, I have couple of generic > comments - please see below. > > Thank you, > Jan > > > [1] In general, I think it might be useful, if the motivation for > introducing generic error service is expressed, e.g. > > * why we need this error service > * what is the advantage of using it > * what existing problems it is going to solve
Good point I'll add more on these questions. > > I think having this information available might be helpful to understand > why/if there is a need for it. > > [2] It is mentioned that the error structure will contain at least > following information: > * failure type > * failure ID (error number) > * where the failure happened > * what went wrong > * how to fix it (if possible) or report it > > How this information will map to the proposed err_info and err_data > structures ? > > [3] To be honest, I don't quite understand how the error service > will be plugged into the overall infrastructure - how the process and > data flow will look like - I think it might be useful to provide > some kind of 'case study' or example - e.g. how libbe is going to > consume it in particular failure scenario. > I think what may be helpful here in addition to an example from libbe or AI would be a drawing that shows how all this fits together. I'll create this and attach it to the design as well as adding a couple of examples. I think for examples it might be best to add one for libbe as well as one for AI. Thanks for the comments! -evan
