...
Basically the thought is there is a direct translation between the RPC spec and the web service spec
Why this instead of RESTful?
- It will save everyone time=money if we can have an automatic translation between the structs/rpc and the data formats/transports. We will probably eventually have more than one format (e.g. SOAP and non-SOAP, XML and JSON, etc)
- REST doesn't do as great with lookup things not by one id (e.g. if you want to lookup by id, or uri, or a composite (with subjects, subjectSource and subjectId)
- Not all HTTP clients can do all HTTP methods PUT/DELETE/PATCH/etc, and even all return codes. i.e. is a 500 an error with the fifer server itself, or a validation problem with the inputs?
hasMember
Determine if a subject is a member of a group.
...