Sam Ruby goes Jeff Foxworthy on REST vs. SOAP
March 23, 2006 § Leave a comment
SAM got a little wistful today about this ancient post where he hoped that the REST vs.
SOAP debate would focus on substantive issues. [Read more] to see why he isn’t
giving up his day job…
SOAP debate would focus on substantive issues. [Read more] to see why he isn’t
giving up his day job…
From Sam
Ruby:
Rest vs RPCÊ
In
reality, there aren’t two sides.Ê There are at least
four.Ê
Ruby:
Rest vs RPCÊ
In
reality, there aren’t two sides.Ê There are at least
four.Ê
? Everything is a resource
? Everything is a get
? Everything is a message
? Everything is a procedure
Furthermore, everything doesn’t fit into such neat
little buckets.Ê Anyway, each of these points of view are limiting in some
way that their adherents are typically too blind to see.Ê If all you have
is a hammer, then everything looks like a nail, and all that.
little buckets.Ê Anyway, each of these points of view are limiting in some
way that their adherents are typically too blind to see.Ê If all you have
is a hammer, then everything looks like a nail, and all that.
Telling these guys apart is sometimes difficult.Ê
Here’s a few clues.Ê Read them along the lines of a
Jeff
Foxworthy “you might be a redneck
if…”
Here’s a few clues.Ê Read them along the lines of a
Jeff
Foxworthy “you might be a redneck
if…”
?
You might be a Resource guy if you actually use HTTP
PUT
You might be a Resource guy if you actually use HTTP
PUT
?
You might be a Get guy if you use URLs to request
parameterized actions
You might be a Get guy if you use URLs to request
parameterized actions
?
You might be a Message guy if you actually use XML
attributes
You might be a Message guy if you actually use XML
attributes
?
You might be a Procedure guy if you feel you must
encode XML in order to pass it as a parameter
You might be a Procedure guy if you feel you must
encode XML in order to pass it as a parameter
iHack, therefore iBlog 
Leave a Reply