John Ericson f7b8f8aff6 Introduce separate Serve protocol serialisers ... To start, it is just a clone of the common protocol. But now that we have the separate protocol implementations, we can add versioning information without the versions of one protocol leaking into another. Using the infrastructure from the previous commit, we don't have to duplicate code for shared behavior. Motivation: No more perverse incentives. [0] did some awkward things because the serialisers did not store the version. I don't want anyone making changes to be pushed towards keeping the serialization logic with the core data types just because it's easier or the alternative is tedious. The actual versioning of the Worker and Serve protocol serialisers (Common remains unversioned as the underlying mini-protocols are not versioned) will happen in subsequent commits / PRs. [0]: fe1f34fa60		2023-10-10 11:52:45 -04:00
..
common-protocol	Unit test the "common protocol" too	2023-10-09 16:57:03 -04:00
serve-protocol	Introduce separate Serve protocol serialisers	2023-10-10 11:52:45 -04:00
worker-protocol	Enable most of the third BuildResult worker protocol test	2023-10-04 18:03:50 -04:00