Mark Baker commented on my post about Web services and REST over on his blog. He says:
To the second point, there actually is a critical reason (in addition to the "hide the XML" problem) why SOA/WS cannot be as simple as REST; that the architectural constraints which induce the bulk of the simplicity in REST (uniform interface, self-description), are eschewed by SOA/WS. Isn't it ironic that their raison d'etre - service specific interfaces - is the reason they will fail to see widespread deployment? I think so. 8-)
Two comments...
First, I think the recent discussion about delivering RSS through NNTP or other protocols beyond HTTP point out the limitations of that protocol and, perhaps REST as a model for all delivery of information.
Second, I actually think that WS do have a simple set of operations: input/output, input, output and output/input. That's it.
Posted
Sep 30 2004, 12:30 PM
by
tim-ewald