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
Is your feature request related to a problem? Please describe.
On the current codes, the api-server and some ledger-connectors (besu, quorum, corda, ...) does not have socket.io connection to cmd-api-server. This communication channel is needed for developing the APIs of sendSyncRequest, sendAsyncRequest, and startMonitor as these are developed in ledger-connector-go-ethereum, ledger-connector-sawtooth, ledger-connector-fabric-socket via socket.io connection to cmd-socket-server.
This feature was already developed in ledger-connectors socket.io version, but in case of merging those codes as #1502, we need to develop it.
c.f. ledger-connector-besu has socket.io connection feature but this connection is closed on the components of ledger-connector-besu itself.
Is your feature request related to a problem? Please describe.
On the current codes, the api-server and some ledger-connectors (besu, quorum, corda, ...) does not have socket.io connection to cmd-api-server. This communication channel is needed for developing the APIs of sendSyncRequest, sendAsyncRequest, and startMonitor as these are developed in ledger-connector-go-ethereum, ledger-connector-sawtooth, ledger-connector-fabric-socket via socket.io connection to cmd-socket-server.
This feature was already developed in ledger-connectors socket.io version, but in case of merging those codes as #1502, we need to develop it.
Describe the solution you'd like
Add the socket.io connection to the above components
The text was updated successfully, but these errors were encountered: