Skip to content

Resume

Jump to bottom
Lisselde_E edited this page Sep 24, 2026 · 1 revision

断点续传

断点续传用于文件传输（同步与投递），解决传输中断后需要从头重传的问题：中断后已传部分保留，恢复连接后从断点继续，而不是重头开始。

一、工作机制

  1. 传输中断（网络抖动、对端退出、应用关闭）时，接收端保留已收到的数据为临时文件（*.tcp_* 前缀），不丢弃；
  2. 连接恢复后，接收端带上已传进度（offset）重新发起请求；
  3. 发送端从该 offset 继续发送剩余字节，直至文件完整；
  4. 完成后临时文件自动转为正式文件。

续传尝试次数

  • 一次传输最多自动续传 3 次；
  • 仅在有真实进度（已传部分字节）时续传；若无任何进度或会话已失效，不会对已断开方反复连接；
  • 3 次尝试仍失败，本次传输结束，不会无限重试。

二、适用范围

  • 同步：目录文件增量传输；
  • 投递：经胶囊栏投递的文件（图片 / 文件）；
  • 标准版与 Pro 均支持。

三、用户需要做什么

  • 一般无需操作。中断后程序自动续传，进度条会反映已传部分继续推进；
  • 若连续多次中断，可稍等网络稳定后重试，或重新发起一次传输；
  • 中途发现传输失败，可从投递列表重试，已传部分仍可续传。

四、常见疑问

中断后临时文件会残留吗？ 续传完成或传输失败清理时，临时文件会被清理；若程序异常退出可能残留 *.tcp_* 文件，重启后同步会自动处理（作为未完成传输清理或继续）。

手动取消算中断吗？ 主动取消（接收端取消）会结束本次传输并清理临时文件，不属于可续传的中断。

标准版没有去中心化，也能续传吗？ 能。断点续传是传输层机制，与数据路径（经主机转发 / 端到端直连）无关，两版均具备。

Resumable Transfer (English)

Resumable transfer applies to file transfer (sync and delivery). When a transfer is interrupted, the received portion is kept and the transfer resumes from the breakpoint after the connection is restored, instead of starting over.

1. How It Works

  1. When a transfer is interrupted (network jitter, peer exit, app close), the receiver keeps the already-received data as a temporary file (*.tcp_* prefix) instead of discarding it;
  2. Once the connection is restored, the receiver re-requests with the progress offset;
  3. The sender continues sending from that offset until the file is complete;
  4. When finished, the temporary file becomes the final file.

Attempt limit

  • Each transfer automatically resumes at most 3 times;
  • It resumes only when there is real progress (some bytes already received). Without any progress, or if the session is no longer valid, it does not repeatedly connect to a dead peer;
  • If all 3 attempts fail, the transfer ends; there is no unlimited retry.

2. Scope

  • Sync: incremental transfer of directory files;
  • Delivery: files delivered via the capsule bar (images / files);
  • Supported by both Standard and Pro.

3. What You Need to Do

  • Nothing, normally. After an interruption the program resumes automatically; the progress bar continues from the transferred part;
  • If interruptions keep happening, wait for the network to stabilize and retry, or re-initiate the transfer;
  • If a transfer fails, retry from the delivery list; the transferred portion can still be resumed.

4. FAQ

Do temporary files remain after interruption? After the transfer completes or fails and is cleaned up, temporary files are removed. If the program exits abnormally, *.tcp_* files may remain; on restart, sync handles them automatically (cleaning up or resuming as incomplete transfers).

Does manual cancellation count as interruption? No. A manual cancel (by the receiver) ends the transfer and cleans up the temporary file; it is not a resumable interruption.

Standard is not decentralized — can it still resume? Yes. Resumable transfer is a transport-layer mechanism, unrelated to the data path (via the host / end-to-end direct); both editions support it.

Clone this wiki locally