Conversation
|
|
感谢 PR！ |
|
下一步，你可以让 browser dialer 支持 SplitHTTP，这样我们就有 ALPN 带 h2 的 browser dialer 了，再加个 streaming request 模式
|
I have actually thought about it, but it cannot be widely used because of lack of mobile support. This seems like the bigger piece of work, and I have not arrived at a satisfying conclusion. Should the mobile browser acquire wakelock? How to do that on iOS? etc I also still don't know if there are any actual issues with utls in Iran, and without mobile support it cannot be tested at a large scale (across ISPs, regions)
Is this so that browser dialer and splithttp can be used more efficiently if no CDN is used? |
|
总之 browser dialer 支持 SplitHTTP 所需代码应该很简单，
对，就只是为了 browser dialer，否则 no CDN 时有更好的选择 此外，SplitHTTP 没有 WebSocket 的 ALPN 问题，这是一大优势，应该写在文档中
|
|
cf workers and other "serverless" things are difficult because there is no global state, each request may hit different worker instance. |
* move to paths instead of querystrings * permit early data on serverside * early data for the client, fix context cancellation
2 participants
as discussed at the end of #3412
/<session>and/<session>/<seq>is used. this is really conservative when it comes to special characters required, but it's difficult to extend IMOctxincorrect, and this caused randomly cancelled requests. This is a bug in 1.8.15 as well. Fixed it by usingcontext.WithoutCancel, and making sure thatdialContextusesctxInnerinstead of the outer scopes' contextThis PR is a breaking change from 1.8.15. Server 1.8.15 is incompatible with client 1.8.16, and vice versa.
this is a bit hard to review, if you want separate PRs let me know. I can maybe build PRs which use each other as base branch, to avoid merge conflicts.