summaryrefslogtreecommitdiff
path: root/src/buildtool/execution_api/execution_service/cas_utils.hpp
AgeCommit message (Collapse)Author
2024-11-14execution_api/execution_service: Implement IWYU suggestionsPaul Cristian Sarbu
2024-09-19Unify logic of adding to CAS in ByteStreamServer and CASServerMaksim Denisov
...by calling the generalized CASUtils's implementation.
2024-09-19Implement CASUtils::Add{Data, File}toCASMaksim Denisov
...that both use the same templated class CASContentValidator.
2024-08-30Replace bazel_re::Digest in CASUtilsMaksim Denisov
...with ArtifactDigest
2024-06-28Use (un)expected for CAS utilsOliver Reiche
2024-04-02LargeBlobs: Use LocalCAS methods to implement split-splice logic of CASUtils.Maksim Denisov
2024-02-26Implement blob splicing protocol at just server sideSascha Roloff
2024-02-26Implement blob chunking algorithm negotiationSascha Roloff
2024-02-26Refactor split and splice implementations.Sascha Roloff
Currently, the implementations of the split and splice operation are both hidden behind the Bazel API implementation. This was sufficient to implement splitting at the server and splicing at the client. In order to support the other direction of splitting at the client and splicing at the server while reusing their implementations, the code needs to be refactored. First, the functionality of split and splice are explicitly exposed at the general execution API interface and implemented in the sub APIs. Second, the implementations of split and splice are factored into a separate utils class.