A. Pagaltzis wrote:

* James M Snell <[EMAIL PROTECTED]> [2005-07-26 01:00]:
part of the issue was what happens if the http response is 200
but the payload is trying to communicate that an error
occurred.

Nothing happens. 200 means no error occured. Returning 200 when
an error did occur is broken and should be fixed on the producer
end. Period. I don’t want to see any compromise on this, ever.

If you want to serve over HTTP, it’s your responsibility to be a
good citizen. There are a lot of people who aren’t, of course;
and some have fair, if invalid reasons for their misbehaviour.
In those cases, there’s good reason to listen to them and try
to accomodate them; but the way to do that is not by legalizing
their transgressions.

Remember the Web Accelerator bruhaha? There are fair reasons for
service implementors to want non-idempotent GETs; but legalizing
non-idempotent GETs is not the way to accomodate them.

Regards,
;-) works for me. I'm really not advocating one way or the other on this stuff... just throwing things out there to help develop the conversation a bit. In that vein, what would an example error entry response look like? just a simple basic entry with no fancy schmancy extension elements required?
- james

Reply via email to