mirror of
https://github.com/zrepl/zrepl.git
synced 2024-11-24 17:35:01 +01:00
One-stop ZFS backup & replication solution
fa4d2098a8
Tear down occurs on each protocol level, stack-wise. Open RWC Open ML (with NewMessageLayer) Open RPC (with NewServer/ NewClient) Close RPC (with Close() from Client()) Close ML * in Server: after error / receive of Close request * in Client: after getting ACK for Close request from Server Close RWC To achieve this, a DataType for RPC control messages was added, which has a separate set of endpoints. Not exactly pretty, but works for now. The necessity of the RST frame remains to be determined. However, it is nice to have a way to signal the other side something went terribly wrong in the middle of an operation. Example: A frameBridingWriter fails to read the next chunk of a file it is supposed to send, it can just send an RST frame to signal this operation failed... Wouldn't trailers make sense then? |
||
---|---|---|
cmd | ||
docs | ||
jobrun | ||
rpc | ||
scratchpad | ||
sshbytestream | ||
util | ||
zfs | ||
.gitignore | ||
.gitmodules | ||
LICENSE | ||
main.go | ||
README.md |
zrepl
ZFS dataset replication. Not a shell script.