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
While sendAndSubscribe inherently has a different API than fcl.tx, there are actually some techniques that can be leveraged to subscribe to an already sent transaction.
When a TX is sent by FCL, store a cache of Map<TxID, Tx> (or an alternaive is to just lookup the transaction from AN, but this could be really flakey + extra requests and only serves a narrow case where TX is not sent by FCL)
Cache possibly belongs in SDK? (this could accomodate manual SDK sending as well as fcl.mutate)
In fcl.tx use sendAndSubscribe instead, but just pull from the cache to get original TX body
The text was updated successfully, but these errors were encountered:
jribbink
changed the title
[Streaming] Replace fcl.tx with sendAndSubscribe
[Streaming] Replace fcl.tx implementation with sendAndSubscribe
Nov 15, 2024
While sendAndSubscribe inherently has a different API than fcl.tx, there are actually some techniques that can be leveraged to subscribe to an already sent transaction.
Map<TxID, Tx>
(or an alternaive is to just lookup the transaction from AN, but this could be really flakey + extra requests and only serves a narrow case where TX is not sent by FCL)fcl.tx
usesendAndSubscribe
instead, but just pull from the cache to get original TX bodyThe text was updated successfully, but these errors were encountered: