From 4c5d9fa356bcb6dcd746129dde934412b44fdd35 Mon Sep 17 00:00:00 2001 From: Florian Klink Date: Thu, 1 Feb 2024 13:30:10 +0200 Subject: feat(tvix/castore/docs/verified-streaming): clarify reply "given chunksize" is misleading here. It's up to the backend to decide if it does chunking at all, and how it chunks. Change-Id: I4f130ca9ac34db79f18ef1d6475295806ac7f9a4 Reviewed-on: https://cl.tvl.fyi/c/depot/+/10728 Autosubmit: flokli Reviewed-by: Connor Brewster Tested-by: BuildkiteCI --- tvix/castore/docs/verified-streaming.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tvix') diff --git a/tvix/castore/docs/verified-streaming.md b/tvix/castore/docs/verified-streaming.md index 24197d90a013..fc766fff5d5a 100644 --- a/tvix/castore/docs/verified-streaming.md +++ b/tvix/castore/docs/verified-streaming.md @@ -73,7 +73,7 @@ having the covering range of aligned 1K blocks. ## Actual implementation -> BlobService.Read() gets the capability to read chunks as well - -> BlobService.Stat() can hand out a list of chunks with a given chunksize if asked so. + -> BlobService.Stat() can reply with a list of chunks. rq params: send_bao bool server should be able to offer bao all the way down to 1k some open questions w.r.t sending the whole bao until there, or just -- cgit 1.4.1