fix(broker):Added windows pipe communication #50 #201
Closed
Conversation
This file contains 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
…which nicely encapsulates the operations of windows pipe and returns the connection type net.Conn.
|
|
|
StartPipeSocketListening A channel created for the windows system |
|
All checks have passed，I added pipe socket conditions for different systems @chowyu08 |
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.
I used the open source project npipe, which nicely encapsulates the operation of the Windows pipe and returns a net.Conn type connection, compatible with hmq, making it very convenient for Windows users like us. I noticed that in the last committed Unix socket communication, the name UnixSocket is not standard, it should be unixSocket. I'm terribly sorry.