Use ConcurrentLinkedQueue (FIFO) instead of ArrayList. #3
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
added 14 commits
February 6, 2018 21:34
…urrent functionality with the possibility to pop (i.e. get and remove) received messages.
… also not really hurt
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.
Use a unbounded FIFO Queue object (ConcurrentLinkedQueue) as backing data structure instead of ArrayList. This extends the current functionality with the possibility to pop/poll (i.e. get and remove) single received messages. Before, one could only clear all messages.
The Queue Interface is more or less a superset of the List interface, so existing code can be adapted very easily.