This repository has been archived by the owner on Aug 31, 2021. It is now read-only.
🚩 add the ability to store and watch synced data #85
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.
A really interesting little idea.
This adds the ability to use a new
remit.watch
command. It functions similarly to a listener, but is intended for a block of JSON synced between multiple processes.Multiple processes accessing the same
my.synced.data
there will all receive the same JSON block. To change it, any of the processes can send an emission tomy.synced.data
and all of the watchers will receive the update.Testing it out in a tiny little environment with servers spinning up and down. It's a super-interesting little idea, though not sure how viable/useful it is in the real world.