Currently, the key lookup implementation (token/services/network/fabricx/lookup) uses the fabric delivery service to get access to all transactions and search for the requested key.
The goal of this Issue is to replace the existing implementation with a new one based on the fabricx query service (as used in token/services/network/fabricx/finality/finality.go).
The interfaces to implement are defined in token/services/network/fabric/lookup, ListenerManagerProvider and ListenerManager. The implementation of ListenerManager should return true to calls to PermanentLookupListenerSupported. When calling AddPermanentLookupListener, the manager should schedule a recurrent job that checks the request key and invokes the listener if a new version of the key is found.
For AddLookupListener the query service should be invoked more ofter until either the key is available of a timeout happens.
Currently, the key lookup implementation (
token/services/network/fabricx/lookup) uses the fabric delivery service to get access to all transactions and search for the requested key.The goal of this Issue is to replace the existing implementation with a new one based on the fabricx query service (as used in
token/services/network/fabricx/finality/finality.go).The interfaces to implement are defined in
token/services/network/fabric/lookup,ListenerManagerProviderandListenerManager. The implementation of ListenerManager should return true to calls toPermanentLookupListenerSupported. When calling AddPermanentLookupListener, the manager should schedule a recurrent job that checks the request key and invokes the listener if a new version of the key is found.For
AddLookupListenerthe query service should be invoked more ofter until either the key is available of a timeout happens.