avoid padding in servePut
This means that when the client sends a truncated data to indicate invalidity, DATA is not passed the full expected data. That leaves the P2P connection in a state where it cannot be reused. While so far, they are not reused, they will be later when proxies are supported. So, have to close the P2P connection in this situation.
This commit is contained in:
parent
efa0efdc44
commit
a01426b713
4 changed files with 42 additions and 31 deletions
|
@ -28,10 +28,6 @@ Planned schedule of work:
|
|||
|
||||
## work notes
|
||||
|
||||
* servePut and clientPut pad the data to indicate when it's not valid.
|
||||
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
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue