Salutation
Personalities
Salutation Personalities
When a Client wants to use a Service provided by Salutation Equipment, the Salutation Manager can establish a virtual data pipe between a Client and a Service. This is called a Service Session. Commands, responses and data are exchanged between Clients and Services on these data pipes in blocks called Messages. Messages have a defined format and are exchanged under a defined protocol. Such definitions of message exchange format and protocol are called Personality Protocols. The Salutation Manager may be instructed to operate in one of three distinct Personality Protocols while managing this data pipe.
Native Personality
The Salutation Manager may set up the data pipe and then step into the background, allowing the Client and Service to manage the message stream and data formats. This is known as Native Personality. This personality is useful when Salutation Manager is used solely to discover the capabilities of other Network Entities, with the applications, services and devices managing the interactions between Clients and discovered Services.
Messages are exchanged between Clients and Services directly, without the involvement of the Salutation Manager. Messages are NOT carried by the Salutation Manager Protocol under a Native Personality Protocol. Message exchange is native data in native packets.
Note: Although the Salutation Manager Protocol is not used with the Native Personality Protocol, the Salutation Manager Protocol may be used by the Client to find or query the Service prior to requesting the Service. Coexistence of message exchange under a Native Personality Protocol and the use of Salutation Manager Protocol is dependent on the type of underlying transport and the native protocol used.
Emulated Personality
The Salutation Manager may set up the data pipe and manage the message stream, while the data formats are selected and controlled by the Client and Service. This is known as Emulated Personality. This personality is useful when a common messaging protocol does not exist between a Client and a discovered Service.
All Messages under an Emulated Personality Protocol are carried by the Salutation Manager Protocol. Message exchange is native data in Salutation packets.
Under the Emulated Personality Protocol, Client Messages go through Salutation Managers, however the Salutation Manager never inspects the contents or semantics of Messages.
Salutation Personality
The Salutation Manager may set up the data pipe, manage the message stream, and provide the data format definition for Client/Service interaction. This is known as Salutation Personality. This personality is the subject of the Salutation Architecture and provides a common messaging protocol and common data format between a Client and a discovered Service.
Under the Salutation Personality Protocol, message format and exchange protocol are defined by the Salutation Architecture. Some Salutation Personality Protocol commands, parameters, and protocols are common across Functional Unit types under a common framework. All Messages under the Salutation Personality Protocol are carried by the Salutation Manager Protocol. Message exchange is Salutation data in Salutation packets.
Under the Salutation Personality Protocol, Client Messages go through Salutation Managers, however the Salutation Manager never inspects the contents or semantics of Messages.