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
..
data	Factor our connection code for worker proto like serve proto	2024-05-27 00:43:46 -04:00
common-protocol.cc
content-address.cc	Add Git object hashing to the store layer	2024-02-27 11:27:34 -05:00
derivation.cc
derived-path.cc
downstream-placeholder.cc
local.mk	Commit more stack size in some windows binaries	2024-05-23 17:42:55 -07:00
machines.cc	Restore exposing machine file parsing	2024-05-23 00:03:52 -04:00
nar-info-disk-cache.cc
nar-info.cc
nix_api_store.cc	test/libutil: Add OBSERVE_STRING macro	2024-04-11 17:39:21 +02:00
outputs-spec.cc	Ban building Nix with NDEBUG	2024-03-02 11:22:46 -08:00
path-info.cc
path.cc	Disallow store path names that are . or .. (plus opt. -)	2024-01-31 18:35:19 +01:00
references.cc
serve-protocol.cc	Factor our connection code for worker proto like serve proto	2024-05-27 00:43:46 -04:00
store-reference.cc	Add StoreReference::render	2024-05-22 09:20:15 -04:00
worker-protocol.cc	Factor our connection code for worker proto like serve proto	2024-05-27 00:43:46 -04:00