Added setAttachment and getAttachment to WebSocket interface #627
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.
Description
This allows a WebSocket connection object to have any kind of data associated.
You can now store information of each connection/user and access it when
onMessage
oronClose
is fired.Usage example
Related Issue
#485 Create key/value map in WebSocket
Motivation and Context
I need to store information about each connection, id, name, etc.
I started by open an issue, then @marci4 replied there was an open discussion about my problem here: #485. After reading all it was said about a possible implementation, I did some performance tests between implementing an
HashMap
or creating a getter and a setter to an attachment of type<T>
, and this one was the most efficient by far, with tens and billions of elements.How Has This Been Tested?
I'm using this feature now, and it's working great. I have a
User.java
that I use as the connection attachment, with many variables and some logic, everything is working as expected.Types of changes
Checklist: