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.

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

Cache staking events #10

Open
sihoang opened this issue Apr 18, 2019 · 1 comment
Open

Cache staking events #10

sihoang opened this issue Apr 18, 2019 · 1 comment
Assignees

Comments

@sihoang
Copy link
Member

sihoang commented Apr 18, 2019

It's obviously slow to query event logs from client. We need to cache the events in the backend.

@sihoang sihoang self-assigned this Apr 18, 2019
@sihoang
Copy link
Member Author

sihoang commented Apr 18, 2019

After a lot consideration, the approach is front-end cache because:

  1. Much less effort
  2. Speed has improved a lot

Cons: First visit is slow even though it's way better than before.

So, we need to implement a new endpoint to tell front end if cache needs to be invalidate WeTrustPlatform/staking-dapp#31

We want the invalidate flag to be true when existing causes info are modified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant