Helix Core Server Administrator Guide: Fundamentals (2019.2)

Protocol levels of the Helix server

Each release of the Helix server is assigned a server protocol level. Generally, Helix client and server applications are forward and backward compatible. The protocol level is passed between the Helix Server and the client application so that client application requests meet the requirements of the protocol level.

Release Number	Protocol Level
2019.2	49
2019.1 Patch 2	48
2019.1	47
2018.2	46
2018.1	45
2017.2	44
2017.1	43
2016.2	42
2016.1	41
2015.2	40
2015.1	39
2014.2	38

Release Number	Protocol Level
2014.1	37
2013.3	36
2013.2	35
2013.1	34
2012.2	33
2012.1	32
2011.1	31
2010.2	30
2010.1	29
2009.2	28
2009.1	27
2008.2	26
2008.1	25

Release Number	Protocol Level
2007.2	24
2007.2	23
2006.2	22
2006.1	21
2005.2	20
2005.1	19
2004.2	18
2003.2	17
2003.1	16
2003.1 (early)	15
2002.2	14
2002.1	13
2001.2	12

Release Number	Protocol Level
2001.1	11
2001.	10
2000.1	9
99.2	8
99.1	7
99.1 (early)	6
98.2	5
98.2 (early)	4
97.2	2
97.3	3
97.2	2
97.1	1

Example

When launching a 2006.2 Helix Server with RPC tracing set to level 5 (-vrpc=5), the server protocol level, 22, can be seen in the server2 variable.

p4d -r . -p 1666 -vrpc=5
RpcSendBuffer xfiles = 5
RpcSendBuffer server = 3
RpcSendBuffer server2 = 22
RpcSendBuffer revver = 7
RpcSendBuffer nocase = Perforce Server starting...

Note

This information is useful when developing applications using the Perforce Helix API.

The server protocol level is not related to the upgrade counter. The upgrade counter refers to changes of the database schema. The server protocol level refers the changes in the RPC.

Your search for returned result(s).