[WIP] History api #409
Closed
[WIP] History api #409
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
Florimond
force-pushed
the
history_api
branch
2 times, most recently
from
d0c6e39
to
21db3e9
Compare
This PR adds support for MQTT Retain flag. In order to make retained messages play well with emitter's message history, we consider that the retained messages are just messages with a large TTL (defaults to `30 days` ). The `retain` TTL is configurable in the storage provider, so you can setup a longer or shorter time. 1. The retain flag will only work if the key has `store` permission 2. The subscriptions with `load` permission will default to `last=1` . This is done in order to be compliant with the MQTT spec as the retain message should always be sent to the subscriptions. Now, you can still have `ttl` and `last` options and it should play well with the retained messages, sending everything.
* add max message size as configurable * fix review comments - add limit structure and omitempty * improve comments * fix failing test cases
* support of shared subscriptions * share as per spec * fix short subs
* updated dependencies * update deps * keeping vendor for now * tidy up
* fix large N subscriptions * export Contains * cleanup a bit
So that a status can be requested without passing the "changes" parameter and therefore without touching the Trie.
Signed-off-by: CodeLingo Bot <bot@codelingo.io>
So that when subscribing to presence messages without request a status, there isn't a status message with empty Who array sent anymore.
* add prometheus support * refactored to manage own registry * go mod tidy * removed ProcessCollector as this is only supported on linux
* embed keygen form * Added additional tests * Updated generation responses, fixed router subscription * added html template
* use slice index instead of copy of 2 value in range * fix #305
* Updated dependencies and LWWSet * mesh * remove unsafe pointer arithmetic
* Added v3 license with shuffled salsa cipher * add workflows * edge just on push * separate workflows * fix test error * master only
* Fixes presence notification when peer goes offline * add peer name to event * improved subscription encoding * fix test * fix test
* Refactored survey * fix merge
* added durable CRDT * Add cache for durable * decrement conn
* Added support to block/unblock keys * avoid unnecessary notifications
This PR adds an implementation of "Last Will & Testament" of MQTT to emitter. This handles 2 scenarios: 1. When client is terminated but the broker is alive. 2. When the broker is terminated. In both cases, last will will be sent to the cluster and optionally message will be retained. This uses consistent hashing to determine which peer will send out the last will in case of the broker termination. Moreover, I have done a massive refactoring of the service (long overdue). In this refactoring, all of the handlers and services have been made simpler with clear dependencies (see service/ folder). In addition, all tests for the handlers have been rewritten and they have 100% code coverage.
* upgrade deps * upgrade to 1.16 * upgrade coveralls
CompareAndSwapUint32 instead of just an atomic load of the value, and changing the value later, which was not producing the needed behavior in terms of atomicity. Co-authored-by: Roman Atachiants <roman.atachiants@gmail.com>
* replace inmemory storage * update deps
AppVeyor is not being used anymore
[WIP] Add history api The message history of a channel can be retrieved when subscribing. This API allows requesting the history independently of the subscription request. The code essentially comes from the the subcription handler. TODO: - Write tests. - Actually test to see if it even works, this is just a draft. [WIP] Limiter [WIP] New limiter technique
Florimond
force-pushed
the
history_api
branch
from
21db3e9
to
9d415ab
Compare
Florimond
force-pushed
the
history_api
branch
from
9d415ab
to
7304a50
Compare
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.
[WIP]