Sun Cluster Data Services Developer's Guide for Solaris OS

Message Types That the CRNP Uses

The CRNP uses three types of messages, all of which are XML-based, as described in the following table. These message types are described in more detail later in this chapter. Usage is also described in more detail later in this chapter.

Type of Message	Description
`SC_CALLBACK_REG`	This message takes four forms: `ADD_CLIENT`, `REMOVE_CLIENT`, `ADD_EVENTS`, and `REMOVE_EVENTS`. Each of these forms contains the following information: Protocol version Callback port in ASCII format (not binary format) The `ADD_CLIENT`, `ADD_EVENTS`, and `REMOVE_EVENTS` forms also contain an unbounded list of event types, each of which includes the following information: Event class Event subclass (optional) List of the name and value pairs (optional) Together, the event class and event subclass define a unique “event type.” The DTD (document type definition) from which the classes of `SC_CALLBACK_REG` are generated is `SC_CALLBACK_REG`. This DTD is described in more detail in Appendix F, Document Type Definitions for CRNP.
`SC_EVENT`	This message contains the following information: Protocol version Event class Event subclass Vendor Publisher Name and value pairs list (0 or more name and value pair data structures) Name (string) Value (string or string array) The values in an `SC_EVENT` are not typed. The DTD (document type definition) from which the classes of `SC_EVENT` are generated is `SC_EVENT`. This DTD is described in more detail in Appendix F, Document Type Definitions for CRNP.
`SC_REPLY`	This message contains the following information: Protocol version Error code Error message The DTD (document type definition) from which the classes of `SC_REPLY` are generated is `SC_REPLY`. This DTD is described in more detail in Appendix F, Document Type Definitions for CRNP.

Type of Message

Description

SC_CALLBACK_REG

This message takes four forms: ADD_CLIENT, REMOVE_CLIENT, ADD_EVENTS, and REMOVE_EVENTS. Each of these forms contains the following information:

Protocol version
Callback port in ASCII format (not binary format)

The ADD_CLIENT, ADD_EVENTS, and REMOVE_EVENTS forms also contain an unbounded list of event types, each of which includes the following information:

Event class
Event subclass (optional)
List of the name and value pairs (optional)

Together, the event class and event subclass define a unique “event type.” The DTD (document type definition) from which the classes of SC_CALLBACK_REG are generated is SC_CALLBACK_REG. This DTD is described in more detail in Appendix F, Document Type Definitions for CRNP.

SC_EVENT

This message contains the following information:

Protocol version
Event class
Event subclass
Vendor
Publisher
Name and value pairs list (0 or more name and value pair data structures)
- Name (string)
- Value (string or string array)

The values in an SC_EVENT are not typed. The DTD (document type definition) from which the classes of SC_EVENT are generated is SC_EVENT. This DTD is described in more detail in Appendix F, Document Type Definitions for CRNP.

SC_REPLY

This message contains the following information:

Protocol version
Error code
Error message

The DTD (document type definition) from which the classes of SC_REPLY are generated is SC_REPLY. This DTD is described in more detail in Appendix F, Document Type Definitions for CRNP.