Add RUES dispatch #1704
Merged
Add RUES dispatch #1704
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
ureeves
force-pushed
the
rues-dispatch
branch
3 times, most recently
from
3be9231 to
cf2db5a
Compare
added 4 commits
May 15, 2024 11:26
This is achieved by introducing a formal `RuesEvent` struct and using it as a wrapper for contract events. This also allows the system to be more extensible - beyond contract events - and include more types of data, such as chain data, in the future.
HDauven
approved these changes
May 15, 2024
miloszm
reviewed
May 15, 2024
| mpsc::channel(DISPATCH_BUFFER_SIZE); | ||
|
|
||
| // Join the two event receivers together, allowing for reusing the exact | ||
| // same code when handling them either of them. |
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.
Allows for the client to dispatch events, and receive "response" events on the connected websocket according to the RUES specification. This effectively means the RUES API is, with this PR, just as powerful as the previous API.