InvalidArgumentExceptions--How should we handle it |
||
![]() Cpt SAJChurchey What kind of error messages should the encryption/decryption methods report back to the client? I want to go ahead and code in the exception throws for the functions. I think w/ any null case, the exception message should be an empty string. No real processing is done, and the user probably submitted a null input on accident. It would probably be completely transparent, and the user would just think that it didn't do anything w/ an empty text field. All whitespace may be handled the same way. Invalid input in general, we should report back to the user exactly what kind of input we're looking for "binary digits, hex digits,UTF-16, etc." and that these sets should be separated by whitespace. Cpt SAJChurchey
C/O of Editorial OSI Staff edit0r OSI Feedback Representative Replies:
|
||
| CyberArmy::Forum v0.6 Generated In 0.02293 seconds |