|the user should get a friendly "Sorry" screen, with
instructions to try again, and a way to notify the webmaster
I think it depends on the application. If you are offering
a free service, you can probably get away with this. If you
are offering a service where you have customers that are paying
for the usage of your page, you'll need to have more than
Otherwise, you'll end up with a support department always
trying to figgure out what to tell a customer whenever they
write in and ask what went wrong.
In my experience, the best system is short descriptive
error messages. These give clueful users enough info that they
don't need to request support. It also gives your support
department enough info to go on that they don't have to
spend so much time helping the less-cluefull users (or
bugging the programmers).
Your results may vary.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||