Retained message store extendable #1663
Open
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
|
@chkr1011 What do you think? Does it fit? |
|
Is this progressing? I just had an attempt to use events as an extension method for external storage but it is no good (#1763). The current events work ok as long as one can accept that all retained messages are kept in memory, but now I'm looking for a solution where they can be loaded on demand, i.e. by using the proposed |
Hoseinmj
approved these changes
Jun 27, 2023
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.
See the issue #1660
Now the interface
IMqttRetainedMessagesManagercan be used to build your own retained message store. You can set the implementation inMqttServerOptions.RetainedMessagesManager. If no custom RetainedMessagedManger is set, the current one is used.