When a new version of CVSup comes out, do the clients and the server have to be upgraded at the same time?
Traditionally, all publicly released versions of CVSup have been able to interoperate with each other. However, that became undesirable with the discovery of the unfortunate s1g bug, which was present in all versions of CVSup prior to SNAP_16_1d. CVSup clients which contain the s1g bug create very heavy loads on CVSup servers. To protect the servers from this problem, checks were added to them beginning with version SNAP_16_1e. These newer servers refuse to provide service to any CVSup client which contains the s1g bug. When such a client connects to a SNAP_16_1e or later server, the server terminates the connection immediately and causes the client to display a message explaining the problem. The message includes information about obtaining updated versions of CVSup. CVSup clients also need protection from old servers which would deliver files with incorrect timestamps. Therefore, similar checks were added to the clients, beginning with version SNAP_16_1e. If one of these newer client
