1.7.1 Protocol Versions

Version negotiation is performed by using the server version (section 3.1.5.3.36) method. The client sends its own protocol version in the method name section of the request. The server compares that to the server protocol version and replies to the client. The protocol version that the server uses is given in the response header in the format of (Min(ServerVersion, ClientVersion)). The client is expected to use this version for any remaining communications. If the version of the client or server is not supported, the one with the newer protocol version discontinues the conversation.<1>

The structure of a FrontPage Server Extensions: Website Management Protocol version (as described in section 2.2.2.2.9), as defined, has four parts: a major version, a minor version, a phase number, and a build number. Therefore, a version might look like 1.0.0.3214. Versions grow over time, so 3.0 is considered earlier, or older, than 4.0.

In the FrontPage Server Extensions: Website Management Protocol, the client, server, and protocol each have their own version, although all of them follow the same format. The client and server version are used in the negotiation to determine the protocol version. For details, see section 3.1.5.3.36.

All servers reject any client with a version earlier than 4.0.2.2611, and clients reject any server with a version earlier than 3.0.2.1002. The server returns a V_RPC_CLIENT_TOO_OLD (0x0004000C) error code (see section 2.2.2.2.17.1) if an incompatible client is encountered. If the version of the server is not supported, the client simply ignores the server, and no further communication with the server is attempted.