Excellent Driver
Tim Bray: reachservices is a good example of what the SOA deployments of the future will look like. I think that if there are any protocols, technologies, or standards that turn out not to be necessary for this project, then maybe they’re not that necessary at all.
Let's read the fine print:
- 1.1.7.1 A client application which avails of the IAM service MUST generate complete HTTP 1.1 POST requests and MUST receive and interpret entire HTTP 1.1 Response messages. Not that necessary: HTTP GET
- 1.1.7.2 All traffic to the IAM service MUST (and all traffic
from the IAM service WILL) be encoded using US-ASCII (7 bit)
exclusively and encode common non-US-ASCII characters as empty
<Unicode ch=”xxxx” >element, where the ‘ch’ attribute MUST be encoded using Unicode 3.1 code points. Not that necessary: UTF-8 - 2.3.1.2 The <MessageType> element is the primary identifier by which the IAM service processes the message. Information entered into this element controls the validation, processing, transformation and routing rules, which are applied to a message. This element MUST be present in all Reach envelopes and it MUST only be present once. Not that necessary: URI