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
Implement intelligent long term ABI caching, both natively and through Robo V2.
Native we can use get_raw_abi instead of get_abi, and then create a permanent cache of that ABI stored by its hash. In future requests, when we see a cache entry, the client can make a quick call to get_code_hash to compare the local hash with the remote hash, determining whether the cache should be replaced. IndexedDB or CacheStorage could be used to hold these records in the client long term.
Robo v2 availability would allow us to redirect requests for ABIs (e.g. get_abi/[contract_name]) to caches that have Cache-Control: immutable in the headers, allowing the browser to just perform the caching for us.
Implement intelligent long term ABI caching, both natively and through Robo V2.
get_raw_abi
instead ofget_abi
, and then create a permanent cache of that ABI stored by its hash. In future requests, when we see a cache entry, the client can make a quick call toget_code_hash
to compare the local hash with the remote hash, determining whether the cache should be replaced. IndexedDB or CacheStorage could be used to hold these records in the client long term.get_abi/[contract_name]
) to caches that haveCache-Control: immutable
in the headers, allowing the browser to just perform the caching for us.Internal discussion: https://greymass.slack.com/archives/C045MUS6F0F/p1676444342156639
The text was updated successfully, but these errors were encountered: