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
Currently api (network connection) is opened when user opens extension and closed when user closes the extension. The benefit is there is no unnecessary network connection. The side effect is user may experience waiting time for first balance display (It takes about 3 seconds to establish an api connection).
If we move the api connection to background, that means once user opens browser, the connect will get opened until the browser is closed. Given nowadays most people keep browser opens, api connection is probably ready whenever user opens the extension, which means user does not have to wait the 3 seconds whenever she/he opens the extension.
Another benefit is if user start a transaction in extension, the connection won't be lost if impatient user closes the extension straightaway, which will cause unnoticed tx failure.
The text was updated successfully, but these errors were encountered:
Another benefit would be that user can check the query instantly after the extension is open. It takes time to connect the api, and we cannot rely on loader every time.
Just thought of a downside of this approach - if we keep connection at background, there will be probably many many open connections to rpc endpoints if many people use Speckle. Those open connections will be a big burden on the rpc endpoint.
Currently api (network connection) is opened when user opens extension and closed when user closes the extension. The benefit is there is no unnecessary network connection. The side effect is user may experience waiting time for first balance display (It takes about 3 seconds to establish an api connection).
If we move the api connection to background, that means once user opens browser, the connect will get opened until the browser is closed. Given nowadays most people keep browser opens, api connection is probably ready whenever user opens the extension, which means user does not have to wait the 3 seconds whenever she/he opens the extension.
Another benefit is if user start a transaction in extension, the connection won't be lost if impatient user closes the extension straightaway, which will cause unnoticed tx failure.
The text was updated successfully, but these errors were encountered: