On 5/7/06, Thomas Broyer <[EMAIL PROTECTED]> wrote:
*This* is nice and simple:
{{{
HTTP/1.1 500 Internal Server Error
Server: xxxxxxxxx
Date: xxxxxxxxx
Content-Type: text/plain
Content-Length: 31
Can't connect to the DB server.
}}}
I agree "that" is simple.
But please! please wait. That is not simple as it looks to me.
(1)Not easy for I18N
(2)Not user friendly
(1) In Japan, we have a LOT, I mean A LOT, of charset
commonly used, such as Shift-JIS, EUC-JP, JIS, UTF-X,
etc. If it was a XML document, an XML Parser will take
care of all the messy encoding conversions.Otherwise,
there would be a lot of extra work just to handle an error
message. And there is always a chance of wrong conversion.
Hense, "<?xml version="1.0" encoding="utf-8"?>" has been
saved a lot of as.. butt over here.
(2) A client have no way of knowing what the body is.
Is it meant to be displayed to a user(such as my mather)?
or is it just a junk(such as a core dump or trace log)?
Who is generating it? a proxy maybe?
Yes, it looks simple, and probably easiest way to implement.
But, please remember that first person to see the message is
a user who does not know anything about "DB" or "Server".
And please keep in mind that there is more that one charset
out there.
Thanks you.
