[ABW-1315] Radix Connect requset to CE and response from CE #444
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,78 @@ | ||
| import RadixConnectModels | ||
|
|
||
| extension P2P { | ||
| /// Recipient of sender of an RTC message | ||
| public struct RTCRoute: Sendable, Hashable { | ||
|
There was a problem hiding this comment. A since long missing tuple with the information on HOW to send an RTC message. |
||
| /// The PerPeerPairConnection password. | ||
| public let connectionId: ConnectionPassword | ||
| /// ID to a specific peer **connection** for some PerPeerPairConnection. | ||
| public let peerConnectionId: PeerConnectionID | ||
|
|
||
| public init(connectionId: ConnectionPassword, peerConnectionId: PeerConnectionID) { | ||
| self.connectionId = connectionId | ||
| self.peerConnectionId = peerConnectionId | ||
| } | ||
| } | ||
|
|
||
| /// An incoming message over RTC from some `route`, might have failed | ||
| /// or succeeded to receive and decode, which is why this contains a | ||
| /// `result` and not an `P2P.RTCMessageFromPeer` directly. | ||
| public typealias RTCIncomingMessage = RTCIncomingMessageContainer<P2P.RTCMessageFromPeer> | ||
|
|
||
| /// An incoming Dapp Request over RTC from some `route`, might have failed | ||
| /// or succeeded to receive and decode, which is why this contains a | ||
| /// `result` and not an `P2P.Dapp.Request` directly. | ||
| public typealias RTCIncomingDappRequest = RTCIncomingMessageContainer<P2P.Dapp.Request> | ||
|
|
||
| /// An incoming message over RTC from some `route`, might have failed | ||
| /// or succeeded to receive and decode, which is why this contains a | ||
| /// `result` and not an `P2P.RTCMessageFromPeer` directly. | ||
| public struct RTCIncomingMessageContainer<Success: Sendable & Hashable>: Sendable, Hashable { | ||
| public let result: Result<Success, Error> | ||
| public let route: RTCRoute | ||
| public init(result: Result<Success, Error>, route: RTCRoute) { | ||
| self.result = result | ||
| self.route = route | ||
| } | ||
| } | ||
| } | ||
|
|
||
| extension P2P.RTCIncomingMessageContainer { | ||
| public static func == (lhs: Self, rhs: Self) -> Bool { | ||
| guard lhs.route == rhs.route else { | ||
| return false | ||
| } | ||
| switch (lhs.result, rhs.result) { | ||
| case let (.failure(lhsFailure), .failure(rhsFailure)): | ||
| // FIXME: strongly type messages? to an Error type which is Hashable? | ||
| return String(describing: lhsFailure) == String(describing: rhsFailure) | ||
| case let (.success(lhsSuccess), .success(rhsSuccess)): | ||
| return lhsSuccess == rhsSuccess | ||
|
|
||
| default: return false | ||
| } | ||
| } | ||
|
|
||
| public func hash(into hasher: inout Hasher) { | ||
| hasher.combine(route) | ||
| switch result { | ||
| case let .failure(error): | ||
| hasher.combine(String(describing: error)) | ||
| case let .success(success): | ||
| hasher.combine(success) | ||
| } | ||
| } | ||
|
|
||
| public func unpackMap<NewSuccess>( | ||
| _ transform: (Success) -> NewSuccess? | ||
| ) -> P2P.RTCIncomingMessageContainer<NewSuccess>? { | ||
| switch result { | ||
| case let .failure(error): return .init(result: .failure(error), route: route) | ||
| case let .success(value): | ||
| guard let transformed = transform(value) else { | ||
| return nil | ||
| } | ||
| return .init(result: .success(transformed), route: route) | ||
| } | ||
| } | ||
| } | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
| import RadixConnectModels | ||
|
|
||
| // MARK: - P2P.RTCMessageFromPeer | ||
| extension P2P { | ||
| /// A successfully received and decoded message from a peer | ||
| /// either a `response` or a `request`. | ||
| public enum RTCMessageFromPeer: Sendable, Hashable { | ||
| /// A response from a peer to some request we have sent over RTC | ||
| case response(Response) | ||
|
There was a problem hiding this comment. @GhenadieVP I was able to remove the |
||
|
|
||
| /// A request coming from some peer over RTC | ||
| case request(Request) | ||
|
|
||
| /// A response from a peer to some request we have sent. | ||
| public enum Response: Sendable, Hashable, Equatable, Decodable { | ||
| case connectorExtension(P2P.ConnectorExtension.Response) | ||
| } | ||
|
|
||
| public enum Request: Sendable, Hashable, Equatable, Decodable { | ||
| case dapp(P2P.Dapp.Request) | ||
| } | ||
| } | ||
| } | ||
|
|
||
| extension P2P.RTCMessageFromPeer.Request { | ||
| public init(from decoder: Decoder) throws { | ||
| self = try .dapp(.init(from: decoder)) | ||
| } | ||
| } | ||
|
|
||
| extension P2P.RTCMessageFromPeer.Response { | ||
| public init(from decoder: Decoder) throws { | ||
| self = try .connectorExtension(.init(from: decoder)) | ||
| } | ||
| } | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,45 @@ | ||
| import RadixConnectModels | ||
|
|
||
| // MARK: - P2P.RTCOutgoingMessage | ||
| extension P2P { | ||
| /// A message to be sent to some peer over WebRTC | ||
| /// it might be either a response to some original | ||
| /// incoming request, or it might be a request initiated | ||
| /// by our wallet. | ||
| public enum RTCOutgoingMessage: Sendable, Hashable { | ||
| /// A response to some request that we received from `origin`, | ||
| /// we will use `origin` to identify the RTC channel to send over. | ||
| case response(Response, origin: RTCRoute) | ||
|
|
||
| /// A request initiated by us, sent over RTC using `sendStrategy`. | ||
| case request(Request, sendStrategy: Request.SendStrategy) | ||
|
|
||
| /// A response to some request that we received from `origin`, | ||
| /// we will use `origin` to identify the RTC channel to send over. | ||
| public enum Response: Sendable, Hashable, Encodable { | ||
| /// Response back to Dapps | ||
| case dapp(P2P.Dapp.Response) | ||
| } | ||
|
|
||
| /// A request initiated by us, sent over RTC using `SendStrategy`. | ||
| public enum Request: Sendable, Hashable, Encodable { | ||
| /// Describes the strategy used to find a RTC peer to send a request to. | ||
| public enum SendStrategy: Sendable, Hashable, Equatable { | ||
| /// Sends a request to ALL P2PLinks | ||
| case broadcastToAllPeers | ||
| } | ||
|
|
||
| /// e.g. for Ledger Nano interaction, `PeerConnectionID` is not known | ||
| case connectorExtension(P2P.ConnectorExtension.Request) | ||
| } | ||
| } | ||
| } | ||
|
|
||
| extension P2P.RTCOutgoingMessage.Response { | ||
| public func encode(to encoder: Encoder) throws { | ||
| switch self { | ||
| case let .dapp(response): | ||
| try response.encode(to: encoder) | ||
| } | ||
| } | ||
| } |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
A response is for now typically a response back to a Dapp for some "wallet interaction".