Error Messaged and Error Code design?

RESTful implies that you will leverage the underlying protocol, in this case HTTP. HTTP already has a pre-defined list of status codes. I would leverage that structure, and add ancillary information as required.

RESTful implies that you will leverage the underlying protocol, in this case HTTP. HTTP already has a pre-defined list of status codes. I would leverage that structure, and add ancillary information as required.

Please do not return "200" on an error :-).

...HTML error codes will be useful when there is connectivity error or bad request error. Am I missing something? Can you may be give an example?

– Ved Apr 28 '10 at 8:34.

I am going with simple xml error code return type. So in my code if there is an error , return xml will be error description.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.