Repository navigation
SOCKS inbound: Serialize concurrent mux responses - #7301
Closed
Ar-Atharifard wants to merge 1 commit into
Closed
Ar-Atharifard wants to merge 1 commit into
Ar-Atharifard wants to merge 1 commit into
Conversation
Reuse BufferedWriter with buffering disabled before DispatchLink. Add a concurrent-response regression over WebSocket.
Member
|
这样还是有点怪 应该没人在socks5上使用mux吧（为什么不vless） 可以先缓缓 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Smaller revision of #7297.
SOCKS passes an unsynchronized writer to DispatchLink. Reuse BufferedWriter with buffering disabled to protect concurrent mux responses while keeping immediate writes.
VLESS and mux code are unchanged. Includes one WebSocket regression that fails before the fix and passes 20 repetitions with -race.