Steve (and others following this debate)
 
> Which was the bit I'm trying to get across in saying that SOAP v REST
> is a pointless debate. The consumer of the service cares only about
> what happens, not about the mechanism to achieve it. I'm not arguing
> that REST is wrong and should never be used, just that its not
> actually important enough to argue over the bit in between.
 
Might I suggest that we use the terms:
 
"Access Protocol" to mean the mechanism used to access the resources/capabilities of an application (e.g., WSDL+SOAP or REST)
"Application Protocol" to mean the application effects of access (turn lightbulb on, transfer funds between accounts, register a marry, etc.)
 
I think that the latter are meaningful/of interest to the customer, but the former are not.
 
Rgds
Ashley
__._,_.___


SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to