John Ericson f71b4da0b3 Factor our connection code for worker proto like serve proto ... This increases test coverage, and gets the worker protocol ready to be used by Hydra. Why don't we just try to use the store interface in Hydra? Well, the problem is that the store interface works on connection pools, with each opreation getting potentially a different connection, but the way temp roots work requires that we keep one logical "transaction" (temp root session) using the same connection. The longer-term solution probably is making connections themselves implement the store interface, but that is something that builds on this, so I feel OK that this is not churn in the wrong direction. Fixes #9584		2024-05-27 00:43:46 -04:00
..
common-protocol	Move tests to separate directories, and document	2023-12-01 10:48:58 -05:00
derivation	Document store object content addressing & improve JSON format	2024-05-20 09:34:35 -04:00
machines	Restore exposing machine file parsing	2024-05-23 00:03:52 -04:00
nar-info	Move tests to separate directories, and document	2023-12-01 10:48:58 -05:00
path-info	Move tests to separate directories, and document	2023-12-01 10:48:58 -05:00
serve-protocol	Create unit tests for the serve proto handshake	2024-01-22 12:43:11 -05:00
store-reference	Add StoreReference::render	2024-05-22 09:20:15 -04:00
worker-protocol	Factor our connection code for worker proto like serve proto	2024-05-27 00:43:46 -04:00