You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are probably many solutions to this problem. Long term there may be iota events we can listen for, but that's a ways away.
But currently, requests to the iota node can "pile up" before any of them complete. My suggestion is wait for polling requests to complete before issuing subsequent requests. It would be better if we would wait for each poll to come back, before polling for the same iota addresses again. Basically still poll, but just not on a strict interval, and don't issue subsequent GETs to iota node until the previous has resolved.
Discuss other options in the comments.
The text was updated successfully, but these errors were encountered:
There are probably many solutions to this problem. Long term there may be iota events we can listen for, but that's a ways away.
But currently, requests to the iota node can "pile up" before any of them complete. My suggestion is wait for polling requests to complete before issuing subsequent requests. It would be better if we would wait for each poll to come back, before polling for the same iota addresses again. Basically still poll, but just not on a strict interval, and don't issue subsequent GETs to iota node until the previous has resolved.
Discuss other options in the comments.
The text was updated successfully, but these errors were encountered: