I'm a little confused on how this helped your design doc? It seems like you picked the design that the LLM could best implement?
I was really curious about how it helped you iron out the problems but couldn't figure it out from your description
I was really curious about how it helped you iron out the problems but couldn't figure it out from your description
Then I started seeing issues with how I had phrased the terminal conditions, the client terminating immediately upon reaching the EOF on input file, and not reading any further server messages. I considered making a 3-way ACK to signal end, but instead changed the design to tell it to keep track of outstanding un-acked packets and only send the EOF/EOFACK when there were no outstanding messages.
The design is that the client generates a bunch of "xxhash64" messages for each block of data, and the server replies to each one with either "ok" (I already have that data) or "send" (send me that data). The "send" is replied to with either "data" (here's the data) or "zero" (the block is entirely NUL).