Mostyn Bramley-Moore

@buchgr: any thoughts on this? In particular: * The file format (simple header, manually parsed, room to implement other digests). * The new directory structure (version number in the directory...

> > The file format (simple header, manually parsed, room to implement other digests). > > Is there a good reason to not use protobuf for the header? I didn't...

> There is the delimited protobuf format that's supported at least by the Java implementation in protobuf and recommended in the official docs [1] [2]. It simply prepends the serialized...

I would also prefer not to pull in another dependency for what I hope can be a simple header. But before ruling it out I wonder if riegeli could also...

I haven't performed any benchmarks yet, and I haven't figured out when/where to perform the validation. But I suspect that we will either validate data on the first Get or...

We could implement this naively, but that would mean adding more mutexes around using the settings which may change at any time (or using sync/atomic to access a struct). I...

I haven't thought this through but if you want to avoid downtime, could a specialized proxy work? ie receive requests from clients, and forward them on to bazel-remote, with retries...

Hi, adding some example configurations to the docs is a good idea- I'll try to organise that. To answer your questions, normally I would setup a single bazel-remote instance (with...

Hi, I'm not familiar with nodejs. Are you using bazel to build your app? If so, you can add `--experimental_remote_asset_api` to your bazel-remote flags, and `--experimental_remote_downloader=grpc://your.bazel.remote.host:port` and `--remote_cache=grpc://your.bazel.remote.host:port` to your...

I would have guessed this was core bazel behaviour, but I don't know bazel internals particularly well. Can you point me to a small node project that uses bazel to...