c3a785204e
This will allow having an internal thread speaking P2P protocol, which will be needed to support proxying to external special remotes. No serialization is done on the internal P2P protocol of course. When a ByteString is being exchanged, it may or may not be exactly the length indicated by DATA. While that has to be carefully managed for the serialized P2P protocol, here it would require buffering the whole lazy bytestring in memory to check its length when sending, so it's better to do length checks on the receiving side. |
||
|---|---|---|
| .. | ||
| Chunked | ||
| AWS.hs | ||
| Chunked.hs | ||
| Encryptable.hs | ||
| ExportImport.hs | ||
| Git.hs | ||
| Hooks.hs | ||
| Http.hs | ||
| Messages.hs | ||
| P2P.hs | ||
| Path.hs | ||
| ReadOnly.hs | ||
| Special.hs | ||
| Ssh.hs | ||
| ThirdPartyPopulated.hs | ||