-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#382 auth networking interactor #421
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, little task descriptions in PR's can be helpful
@@ -11,6 +11,7 @@ protocol NetworkInteracting { | |||
func subscribe(topic: String) async throws | |||
func unsubscribe(topic: String) | |||
func request(_ request: RPCRequest, topic: String, tag: Int, envelopeType: Envelope.EnvelopeType) async throws | |||
func requestNetworkAck(_ request: RPCRequest, topic: String, tag: Int) async throws |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to get rid of this kind of function that waits for the network acknowledgement (at least if we want to generalize the interactor). We need to find a better way around to wait for the acknowledgement on calls that need it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure I understand, what you mean by generalize
? isn't this approach generic and interface could be shared by all SDKs?
Add
requestNetworkAck
function that completes with an acknowledgement from the relay network.handles incoming requests and responses to networking interactor and publishes decrypted rpc requests to subscribers