3.2.1.4.1 Updating a Server Entry

Parameters:

  • Bindings [in]: An array of one or more string bindings for this RPC interface. The string bindings can optionally contain endpoint information. The format is described in "String Bindings" in Part 2 of [C706].

  • Interface Identifier [in]: A string that encodes the interface identifier and version of this RPC interface. This string MUST be as specified in RPC Syntax Identifier Attribute (section 2.2.5.1.3).

  • Transfer Syntax [in]: A string that encodes the transfer syntax for this RPC interface; MUST be as specified in RPC Syntax Identifier Attribute (section 2.2.5.1.3).

  • Action [in]: Indicates if the Server Entry is to be modified or deleted.

  • Status [out]: Indicates to the caller if the Server Entry update was successful or if it failed with a specific status code.

In non-directory mode, the server updates its local Entry Cache when requested by a higher-level protocol.

If Action is set to delete the server entry, the server removes all entries in the Entry Cache with any of the bindings specified in the Bindings parameter.

If Action is set to modified, for each binding in the Bindings parameter, find the matching server entry in the Entry Cache. If no matching server entry is found, create a new server entry. For each found or created server entry, update the interface identifier and/or Transfer Syntax.

The server can return the following status codes:

  • RPC_S_OK: Indicates successful completion of modification or deletion of a Server Entry.

  • RPC_S_OUT_OF_MEMORY: Indicates that the Server Entry could not be updated because of an out of memory condition.

  • RPC_S_ENTRY_NOT_FOUND: Indicates that the Server Entry could not be located in the Entry Cache. This error is returned when Action is set to delete the server entry and the server entry cannot be found.