Protocol levels of server and client by release
As part of the initial communication, the client and server negotiate which protocol levels to use so they can understand each other. The logs might show a protocol level instead of a release number. The Table of protocols by release shows the server protocol number and client protocol numbers.
Example of server protocol level
When launching a 2020.1 Helix Server with RPC tracing set to level 5 (-vrpc=5), the server protocol level of 50 appears as the value of the server2 variable.
p4d -r . -p 1666 -vrpc=5
RpcSendBuffer xfiles = 5
RpcSendBuffer server = 3
RpcSendBuffer server2 = 50
RpcSendBuffer revver = 7
RpcSendBuffer nocase =
Perforce Server starting...
The server protocol level is unrelated to the Upgrades counter of the Helix Server Database Schema.
Setting the client protocol level
A later client protocol might provide information in a format that earlier client applications are unable to handle without additional parsing or translation. When using the Perforce Helix API, you can set this value to your required protocol level:
| Using the Perforce Helix API |
|---|
|
ClientAPI::SetProtocol("api","<value>"); |
|
See the example code at ClientApi::SetProtocol( char *, char * ) in Helix Core C/C++ Developer Guide |
By default, the Perforce Helix API uses a protocol level matching the version of the API libraries. Therefore, it is often not necessary to set the protocol level value explicitly.
Table of protocols by release
A client release might use the client protocol associated with an earlier server release. For example, the 2020.2 P4V client uses the client protocol 88, which is associated with the 2020.1 server release.
|
|
