« Why SOAP sucks, why SOAP | Main | Cocoon XML Portal article is »
July 25, 2002
Web Services Architectures: Paul Prescod.
Web Services Architectures: Paul Prescod. And I'm sitting next to Dr. Roy Fielding.
SOAP 1.0/1.1. RPC style. Static endpoints. Dynamic things do not have URIs (like purchase orders). Shows example in C# and example submit request for a purchase order.
SOAP 1.2: is extremely flexible. Choose your own message exchange pattern, choose your own protocol, choose your own methods.
SOAP is becoming too complicated and too "open for everyone" (meaning exisiting protocols from other vendors). Solution: Standardize SOAP subset - use URIs for addressing; use SOAP over HTTP. Nouns cannot be standardized because dependent on industry etc. But verbs can be standardized (insert, update, delete). Moves over to introducing REST.
REST goals: scalability of component interactions, generality of interfaces, independent deployment of components.
REST says:
Interactions are stateless (no dependency on previous messages, better scalability, persistant data via URIs). Resources are identified through URIs (any information that can be named is a resource, all logical constructs in a system should be given URIs). Manipulation through representations (resources are not transmitted over the Web - only representations, many representations have URIs to other representations and are therefore "hypermedia resources"). Self descriptive messages (messages should be explicit and clear, no message history, semantics are predefined and globally known). Hypermedia as the Engine of Application state (servers are stateless and messages can be interpreted without examining history, there is no such thing as a service, there are just resources, clients migrate through a series of steps towards a goal follwing hypertext links).
Posted by Matthew at July 25, 2002 02:26 AM