1.7.1 Protocol Versions

Version negotiation is performed by using the server version method (see section 3.1.5.3.14). 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 the server uses is given in the response header in the form 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.

The structure of a FrontPage Server Extensions Remote Protocol version (see section 2.2.2.2.9), as defined, has four parts: a major version, minor version, phase number, and build number. Thus, a version might look like 1.0.0.3214. Versions grow over time, so 3.0 is considered earlier, or older, than 4.0. To compare versions, begin with the major version, then the minor version, then the phase number, and then the build number to see which one is the latest version.

In the FrontPage Server Extensions Remote 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.14.

All servers reject any client with a version that is earlier than 4.0.2.2611, and clients reject any server with a version that is earlier than 3.0.2.1002. The server returns the error code (0x0004000C) 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.

The FrontPage Server Extensions Remote Protocol components were shipped as part of Windows and as separate web downloads. Only the major and minor version numbers are listed. Except as noted previously, any numbers that meet the requirements (see section 2.2.2.2.9) can be used for the phase and build numbers.

For the remainder of this document, the protocol version will be referred to instead of the Windows version to describe support for protocol functionality.