forked from socketio/socket.io
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the "loopback" flag. #1
Merged
Merged
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
The "loopback" flag is used to emit messages on the local endpoint of a socket; e.g., allowing the server to send a message to the server's handler directly. This is especially useful in conjunction with rooms, as it allows the server to proactively trigger behavior for each socket in a room without having to maintain a separate list of said sockets or relying on the client endpoint to trigger the behavior.
ripfester
added a commit
that referenced
this pull request
May 2, 2018
The "loopback" flag is used to emit messages on the local endpoint of a socket; e.g., allowing the server to send a message to the server's handler directly. This is especially useful in conjunction with rooms, as it allows the server to proactively trigger behavior for each socket in a room without having to maintain a separate list of said sockets or relying on the client endpoint to trigger the behavior.
ripfester
added a commit
that referenced
this pull request
May 2, 2018
The "loopback" flag is used to emit messages on the local endpoint of a socket; e.g., allowing the server to send a message to the server's handler directly. This is especially useful in conjunction with rooms, as it allows the server to proactively trigger behavior for each socket in a room without having to maintain a separate list of said sockets or relying on the client endpoint to trigger the behavior.
ripfester
added a commit
that referenced
this pull request
May 2, 2018
The "loopback" flag is used to emit messages on the local endpoint of a socket; e.g., allowing the server to send a message to the server's handler directly. This is especially useful in conjunction with rooms, as it allows the server to proactively trigger behavior for each socket in a room without having to maintain a separate list of said sockets or relying on the client endpoint to trigger the behavior.
ripfester
added a commit
that referenced
this pull request
May 2, 2018
The "loopback" flag is used to emit messages on the local endpoint of a socket; e.g., allowing the server to send a message to the server's handler directly. This is especially useful in conjunction with rooms, as it allows the server to proactively trigger behavior for each socket in a room without having to maintain a separate list of said sockets or relying on the client endpoint to trigger the behavior.
ripfester
added a commit
that referenced
this pull request
May 3, 2018
The "loopback" flag is used to emit messages on the local endpoint of a socket; e.g., allowing the server to send a message to the server's handler directly. This is especially useful in conjunction with rooms, as it allows the server to proactively trigger behavior for each socket in a room without having to maintain a separate list of said sockets or relying on the client endpoint to trigger the behavior.
ripfester
added a commit
that referenced
this pull request
Sep 2, 2020
The "loopback" flag is used to emit messages on the local endpoint of a socket; e.g., allowing the server to send a message to the server's handler directly. This is especially useful in conjunction with rooms, as it allows the server to proactively trigger behavior for each socket in a room without having to maintain a separate list of said sockets or relying on the client endpoint to trigger the behavior.
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.
The "loopback" flag is used to emit messages on the local endpoint of
a socket; e.g., allowing the server to send a message to the server's
handler directly.
This is especially useful in conjunction with rooms, as it allows the
server to proactively trigger behavior for each socket in a room without
having to maintain a separate list of said sockets or relying on the
client endpoint to trigger the behavior.