>> The idea that a client should break if the schema changes, for example, leads to very brittle systems. Thanks for that, much appreciated. >> The idea that

>> The idea that a client should break if the schema changes, for example, leads to very brittle systems. Thanks for that, much appreciated. >> The idea that a client should break if the schema changes, for example, leads to very brittle systems. That's the point, imagine building the web using string values instead of constants. With constants, if it changes, you immediately get notification from the IDE via the compiler and can fix it straight away. If it's a string, then it's up to the poor testers to find it and good luck, it has to be in a known use case. I think for general communications REST is better than not following any standard by far. For web services though, my money is still on SOAP and I'm a Java/Linux lover not .NET these days, SOAP is still best for Web Services in my view.