I believe the error description string is unstructured extra information as Kyle says.
It's been my experience that the error string is much more important than the error code to work out what is going wrong. The error codes aren't specific enough. So I recommend using the error strings and being as clear as possible about the problem encountered. Regards, -gww -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, July 11, 2007 11:03 AM To: [email protected] Subject: [ltk-d] Error Descirption Is the error description field of a status parameter intended to just provide extra information about what went wrong in case of an error? For example, if a user requests the GPIPortCurrentState in a configuration request to a reader that does not support GPI, is this field intended to have a string such as "cannot process request because this reader does not support GPI"? Or is there some more specific use of this field? Thanks, Kyle ------------------------------------------------------------------------ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
