On Wed, 03 Nov 2004 21:35:07 -0800, Tim Bray <[EMAIL PROTECTED]> wrote:
I'm feeling positive about PaceServiceError, but I have a question: why does it need to use a new custom-built HTTP verb? Why don't we just specify that you POST to the ServiceError URI two name-value pairs, CGI style, either in the URI or the body?
I think a new HTTP method gives us more than routing this message through POST. To err something is not equivalent of posting, and without a method for this, you can't err different resources, but have to err an URI with reference to the resource that is erronous. So instead of:
ERR /feed.atom
you need to do something like this:
POST /cgi-bin/error.cgi Content-Type: application/x-www-form-urlencoded Content-Length: 53
error-document=/feed.atom&description=Ill-formed+XML
I don't think the second example is either simpler, more elegant or more RESTful than the first. Quite the opposite, actually.
-- Asbj�rn Ulsberg -=|=- [EMAIL PROTECTED] �He's a loathsome offensive brute, yet I can't look away�
