We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This may go hand in hand with #11 but with a clear practical goal both for new subscriptions and for "re-synching" subscribers whenever necessary.
This might not be easily done with the recently added allowedPublishers/requestPublish logic. Need to take that into consideration.
allowedPublishers
requestPublish
May imply the creation of something like GET <event-id> in the whole network and as a API method (or at least close to it)
GET <event-id>
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This may go hand in hand with #11 but with a clear practical goal both for new subscriptions and for "re-synching" subscribers whenever necessary.
This might not be easily done with the recently added
allowedPublishers
/requestPublish
logic. Need to take that into consideration.May imply the creation of something like
GET <event-id>
in the whole network and as a API method (or at least close to it)The text was updated successfully, but these errors were encountered: