In the context of inter-operability the central part of our work is the definition of a simple, extensible transfer syntax and a set of associated invocation methods and message types. The transfer syntax allows for simple textual description of structured and typed data. It is broadly similar in expressive power to IIOP but permits client and server to marshall and unmarshall without shared state. A Nexus message is a compound object with certain required and optional fields. The following is an example of an event generated by a stock-quote service.
Possible values are notification , request , response , and error .
Some of these will require additional fields. A session identifier. Easy to parse and simply map into most languages. Simple to map onto transport protocols. Fields can be added to messages without breaking entities not expecting them.