Autoupdating the UI results in a Dilemma:
Queries against the Blockchain RPC are a lot and each of them takes up a lot of milliseconds, resulting in the situation that the UI is ALWAYS loading, and never keeps up with the speed of the blockchain.
Here are some Ideas:
View - Contracts
Maybe Contracts that deliver more information at once are much faster than having
Resolving logical dependencies
Some Data cannot change during
Change Counter
We are working on a concept of having an ChangeID for different topics that increments with each change.
Therefore, if we get a new Block, and we figure out that the ChangeID has not been incremented, than we know, that the data in our cache is up to date.
Autoupdating the UI results in a Dilemma: Queries against the Blockchain RPC are a lot and each of them takes up a lot of milliseconds, resulting in the situation that the UI is ALWAYS loading, and never keeps up with the speed of the blockchain.
Here are some Ideas:
View - Contracts
Maybe Contracts that deliver more information at once are much faster than having
Resolving logical dependencies
Some Data cannot change during
Change Counter
We are working on a concept of having an ChangeID for different topics that increments with each change. Therefore, if we get a new Block, and we figure out that the ChangeID has not been incremented, than we know, that the data in our cache is up to date.