avoid padding in clientPut

Instead truncate when necessary to indicate invalid content was sent.
Very similar to how serveGet handles it.
This commit is contained in:
Joey Hess 2024-07-22 11:47:24 -04:00
parent 726c815a7f
commit efa0efdc44
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 31 additions and 22 deletions

View file

@ -32,6 +32,8 @@ Planned schedule of work:
That should not be necessary, they should always be able to truncate the
data.
* clientPut needs to seek to the requested offset in the file.
* Implement: servePutOffset, serveLockContent
* A Locker should expire the lock on its own after 10 minutes initially.