Hi,

I'm working on the linked image functionality with Ed Pilatowicz and I've
got to a point where I would like some feedback on approaches to error
messages/exceptions.

I've included portions of a recent email exchange with Ed, to help motivate
this discussion...

+++START+++

> > - why "code" values?  i'd rather have informative error messages than       
> >   random code values that mean nothing to consumers.                        
> >                                                                             
>                                                                               
> Coded error messages have some advantages over just text. Clear problem       
> communication being one of the advantages, but also elimination of            
> uncertainty when multiple languages are involved. Also, this is a code        
> plus informative text, not just a code.                                       
>                                                                               
> Example:                                                                      
>                                                                               
> LI001: img1. ERROR: this is not a valid name for a linked image : __bad       
>                                                                               
> seems very clear to me. The code helps in telephone/written communications    
> (if required) and the text clearly indicates the fault.                       
>                                                                               
> This is the standard error reporting approach used by all kinds of            
> applications, e.g.: Oracle database, Apache, etc...                           
>                                                                               
> I used to work in support for a database software company and an error        
> code was always much more useful than some (usually garbled/mangled)          
> error text. The text is helpful to help the user resolve the problem          
> him/herself, but the code is essential for remote support.                    
>                                                                               
> If you really don't want error codes, then we can ditch them, but I           
> think there are many advantages, especially in a support context.             
>                                                                               
                                                                                
but does anything else in pkg do this?  i can understand the                    
argument/desire for this, but then shouldn't every error defined in             
api_errors have an error code associed with it?  sounds like a general          
pkg api rfe to me.                                                              

+++END+++

As Ed points out, it would be strange to have just the linked image errors
reporting formatted error codes (LIXXX, etc...) and not other messages
from the client.

I'd appreciate opinions from the core pkg development team on this subject.
If there's no will/desire for such messages in the core group, then we
shouldn't use them. If they are deemed to be useful, then I'll raise an
RFE.

Thanks for any feedback,

Gary
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to