Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

subscribe to past/future chain-events #46

Open
marc0olo opened this issue Jul 23, 2019 · 4 comments
Open

subscribe to past/future chain-events #46

marc0olo opened this issue Jul 23, 2019 · 4 comments
Labels
enhancement New feature or request

Comments

@marc0olo
Copy link
Member

marc0olo commented Jul 23, 2019 •
edited
Loading

No description provided.

@marc0olo marc0olo added the enhancement New feature or request label Jul 24, 2019
@marc0olo
Copy link
Member Author

subscribing to chain-events is supported by the aepp-middleware. see docs:

@marc0olo
Copy link
Member Author

we might also think about providing a polling mechanism to obtain chain-updates from the nodes. personally I prefer the approach to get this data through the middleware.

@marc0olo
Copy link
Member Author

https://forum.aeternity.com/t/best-practice-obtaining-filtering-and-subscribing-to-historic-new-chain-data/4215

@marc0olo marc0olo changed the title add WebSocket support add support to subscribe on past/future chain-events Aug 1, 2019
@marc0olo marc0olo changed the title add support to subscribe on past/future chain-events subscribe to past/future chain-events Aug 1, 2019
@mitch-lbw
Copy link
Member

We plan to provide both mechanisms, polling and subscription to the middleware.
This should be parametrized via config, as well as the waiting time

@mitch-lbw mitch-lbw added this to the v2.1.0 milestone Sep 23, 2019
@marc0olo marc0olo removed this from the v2.2.0 milestone Mar 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@marc0olo @mitch-lbw