3.2.4.1 Catalog Version Negotiation
Before making any calls to the server, a COMA server MUST ensure that it has performed catalog version negotiation, by checking the value of the negotiated catalog version for the session, as specified in section 3.2.1.1, with the following exceptions.
Exception |
Notes |
---|---|
Used for catalog version negotiation. |
|
Used for capability negotiation. |
|
Used for capability negotiation. |
|
Used for capability negotiation. |
|
Sets the import target partition identifier, as specified in section 3.1.1.5. |
|
Used to validate a user account name and password. |
|
Used to synchronize with the server. |
|
Used to determine if a file is safe to delete. |
|
Used to flush the server's local cache of partition user information. |
|
Used to get a list of software restriction policy levels supported by the server. |
|
Used to get a list of component configurations for a component. |
|
Used to control instance load balancing. |
|
Used to control instance load balancing. |
|
Used to control instance load balancing. |
|
Used to control instance load balancing. |
|
Used to obtain information about and control instance containers. |
|
Used to obtain information about and control instance containers. |
|
Used to obtain information about and control instance containers. |
|
Used to obtain information about and control instance containers. |
|
Used to obtain information about and control instance containers. |
|
Used to obtain information about and control instance containers. |
|
Used to obtain information about and control instance containers. |
|
Used to obtain information about and control instance containers. |
|
Used to obtain information about and control instance containers. |
|
Used to obtain information about and control instance containers. |
|
Used to obtain information about and control instance containers. |
|
Specific to replication. |
|
Specific to replication. |
|
Specific to replication. |
|
Specific to replication. |
|
Specific to replication. |
|
Specific to replication. |
Catalog version negotiation is described in more detail in section 3.1.4.1. On successful completion, the client MUST set the negotiated catalog version for the session in its per-session state.
Each COMA client supports an implementation-specific range of catalog versions.<355> However, not all possible supported ranges are recommended.
For the client, maximum interoperability is provided by supporting multiple catalog versions. In particular, supporting both catalog versions 4.00 and 5.00 enables configuration of servers that support catalog version 4.00 only, and enables configuration of multiple-partition support on servers that support catalog version 5.00.
In summary, a client's supported range of catalog versions SHOULD be one of the following combinations.
Versions |
Comments |
---|---|
3.00 |
|
3.00, 4.00 |
Not recommended for clients that configure multiple partitions on a server.<356> |
3.00, 4.00, 5.00 |
|
4.00 |
Not recommended for clients that configure multiple partitions on a server. |
4.00, 5.00 |
|