Overall, I think this looks good, and should make life for consumers of libbe better.
The one thing that jumped out at me was that it wasn't clear to me why the caller was passing in the cmd str and the op str. Presumably, if the caller's making the call, they already know that information. Do you anticipate using that information in deciding how to fill in the other fields? If it's just for the future logging work, I'm not sure that's needed, but I don't have strong objections to it really. Mostly, I just wonder as we add more layers whether we'll end up in a situation where we'll be logging failures in N redundant places. Thanks, Brock Evan Layton wrote: > > Here is the functional/design spec for the BE error and observability > project. > > It's a first version and does include some design elements for what > will eventually become the error handling and logging service for the > Caiman Unified Design project. However this project is not intended to > provide that error handling and logging but just the beginnings of it > and the ability to mesh easily with it. > > I would like to get any comments by the end of the day on Friday (8/21). > > Thanks! > -evan > > ------------------------------------------------------------------------ > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
