Handling incorrect messages

[mike_k]

Originally Posted by nomis52

I agree with Eric. Responders should be strict in what they accept. Anything else encourages sloppy programming on the controller side.

I agree with you, to some degree...

Problem is, that out in the real world the controller is not the piece of equipment that will get the blame if your responder does not work, the user just knows that all other responders he had do work... Hence, the user will blame the responder that does not work.

When all responders behave the same way (that is when the standard is no longer open for interpretation), then the controller will get the blame.

Compare with the web browser issues... We, who know the details, know that when a site that is W3C compliant that does not show up correctly in IE, but is Webkit based browsers etc, it is IE that is the fault, but the general user does not understand that.