I am designing an application which will upload files to a remote server
(incidentally HTTP post if that makes any difference). This is a "client
application" which, hopefully, hundreds of people will be using within 1-2
years and maybe even more as my employer's main product becomes available in
different languages/countries.
Having never made this specific type of application before - I am afraid
that I will overlook some sort of error handling and user information that
is needed.
Is there a standard "template" for error handling, or some sort of a
checklist? What would be nice would be a list of possible errors and
examples on how to catch and report them.
Now, of course I have considered looking on MSDN for every conceivable error
that could be thrown - but I doubt that is practical or necessary. (If that
is what I should be doing, then by all means tell me so!) I tried this a
while back in MFC C++ VS 6.0 and found that I had dozens of errors that
never ever returned, so the effort translating them was wasted - and some
errors that I had missed because I was focusing so exclusively on places
that I was expecting thrown exceptions. Also I am worried about getting too
specific, a "disk read error" on a corrupted file is useful to the user,
more detailed information may simply confuse the user partiularly if they
are not tech savvy.
--
LTP
:)
