|
| 1 | +import Ably |
| 2 | + |
| 3 | +// I'm not too keen on this class in the way it is... I had a few difficulties keeping a mutable status and error on the class (due to Sendable conformance). I had to resort to using an actor to manage the status and error. This then meant needing to change the `Connection` protocol so `state` and `error` have async getters. To make things more complicated, Swift supports async getters but not async setters (and it doesn't allow you to mix a sync setter with an async getter). You call the relevant methods on the actor to update the status and error. We should revisit this as part of wider concurrency concerns here: https://github.com/ably-labs/ably-chat-swift/issues/49 |
| 4 | +internal final class DefaultConnection: Connection { |
| 5 | + // (CHA-CS2a) The chat client must expose its current connection status. |
| 6 | + internal var status: ConnectionStatus { |
| 7 | + get async { await connectionStatusManager.status } |
| 8 | + } |
| 9 | + |
| 10 | + // (CHA-CS2b) The chat client must expose the latest error, if any, associated with its current status. |
| 11 | + internal var error: ARTErrorInfo? { |
| 12 | + get async { await connectionStatusManager.error } |
| 13 | + } |
| 14 | + |
| 15 | + private let realtime: any RealtimeClientProtocol |
| 16 | + private let timerManager = TimerManager() |
| 17 | + private let connectionStatusManager = ConnectionStatusManager() |
| 18 | + |
| 19 | + internal init(realtime: any RealtimeClientProtocol) { |
| 20 | + // (CHA-CS3) The initial status and error of the connection will be whatever status the realtime client returns whilst the connection status object is constructed. |
| 21 | + self.realtime = realtime |
| 22 | + Task { |
| 23 | + await connectionStatusManager.updateStatus(to: .init(from: realtime.connection.state)) |
| 24 | + await connectionStatusManager.updateError(to: realtime.connection.errorReason) |
| 25 | + } |
| 26 | + } |
| 27 | + |
| 28 | + // (CHA-CS4d) Clients must be able to register a listener for connection status events and receive such events. |
| 29 | + internal func onStatusChange(bufferingPolicy: BufferingPolicy) -> Subscription<ConnectionStatusChange> { |
| 30 | + let subscription = Subscription<ConnectionStatusChange>(bufferingPolicy: bufferingPolicy) |
| 31 | + |
| 32 | + // (CHA-CS5) The chat client must monitor the underlying realtime connection for connection status changes. |
| 33 | + realtime.connection.on { [weak self] stateChange in |
| 34 | + guard let self else { |
| 35 | + return |
| 36 | + } |
| 37 | + let currentState = ConnectionStatus(from: stateChange.current) |
| 38 | + let previousState = ConnectionStatus(from: stateChange.previous) |
| 39 | + |
| 40 | + // (CHA-CS4a) Connection status update events must contain the newly entered connection status. |
| 41 | + // (CHA-CS4b) Connection status update events must contain the previous connection status. |
| 42 | + // (CHA-CS4c) Connection status update events must contain the connection error (if any) that pertains to the newly entered connection status. |
| 43 | + let statusChange = ConnectionStatusChange( |
| 44 | + current: currentState, |
| 45 | + previous: previousState, |
| 46 | + error: stateChange.reason, |
| 47 | + retryIn: stateChange.retryIn |
| 48 | + ) |
| 49 | + |
| 50 | + Task { |
| 51 | + let isTimerRunning = await timerManager.hasRunningTask() |
| 52 | + // (CHA-CS5a) The chat client must suppress transient disconnection events. It is not uncommon for Ably servers to perform connection shedding to balance load, or due to retiring. Clients should not need to concern themselves with transient events. |
| 53 | + |
| 54 | + // (CHA-CS5a2) If a transient disconnect timer is active and the realtime connection status changes to `DISCONNECTED` or `CONNECTING`, the library must not emit a status change. |
| 55 | + if isTimerRunning, currentState == .disconnected || currentState == .connecting { |
| 56 | + return |
| 57 | + } |
| 58 | + |
| 59 | + // (CHA-CS5a3) If a transient disconnect timer is active and the realtime connections status changes to `CONNECTED`, `SUSPENDED` or `FAILED`, the library shall cancel the transient disconnect timer. The superseding status change shall be emitted. |
| 60 | + if isTimerRunning, currentState == .connected || currentState == .suspended || currentState == .failed { |
| 61 | + await timerManager.cancelTimer() |
| 62 | + subscription.emit(statusChange) |
| 63 | + // update local state and error |
| 64 | + await connectionStatusManager.updateError(to: stateChange.reason) |
| 65 | + await connectionStatusManager.updateStatus(to: currentState) |
| 66 | + } |
| 67 | + |
| 68 | + // (CHA-CS5a1) If the realtime connection status transitions from `CONNECTED` to `DISCONNECTED`, the chat client connection status must not change. A 5 second transient disconnect timer shall be started. |
| 69 | + if previousState == .connected, currentState == .disconnected, !isTimerRunning { |
| 70 | + await timerManager.setTimer(interval: 5.0) { [timerManager, connectionStatusManager] in |
| 71 | + Task { |
| 72 | + // (CHA-CS5a4) If a transient disconnect timer expires the library shall emit a connection status change event. This event must contain the current status of of timer expiry, along with the original error that initiated the transient disconnect timer. |
| 73 | + await timerManager.cancelTimer() |
| 74 | + subscription.emit(statusChange) |
| 75 | + |
| 76 | + // update local state and error |
| 77 | + await connectionStatusManager.updateError(to: stateChange.reason) |
| 78 | + await connectionStatusManager.updateStatus(to: currentState) |
| 79 | + } |
| 80 | + } |
| 81 | + return |
| 82 | + } |
| 83 | + |
| 84 | + if isTimerRunning { |
| 85 | + await timerManager.cancelTimer() |
| 86 | + } |
| 87 | + } |
| 88 | + |
| 89 | + // (CHA-CS5b) Not withstanding CHA-CS5a. If a connection state event is observed from the underlying realtime library, the client must emit a status change event. The current status of that event shall reflect the status change in the underlying realtime library, along with the accompanying error. |
| 90 | + subscription.emit(statusChange) |
| 91 | + Task { |
| 92 | + // update local state and error |
| 93 | + await connectionStatusManager.updateError(to: stateChange.reason) |
| 94 | + await connectionStatusManager.updateStatus(to: currentState) |
| 95 | + } |
| 96 | + } |
| 97 | + |
| 98 | + return subscription |
| 99 | + } |
| 100 | +} |
| 101 | + |
| 102 | +private final actor TimerManager { |
| 103 | + private var currentTask: Task<Void, Never>? |
| 104 | + |
| 105 | + internal func setTimer(interval: TimeInterval, handler: @escaping @Sendable () -> Void) { |
| 106 | + cancelTimer() |
| 107 | + |
| 108 | + currentTask = Task { |
| 109 | + try? await Task.sleep(nanoseconds: UInt64(interval * 1_000_000_000)) |
| 110 | + guard !Task.isCancelled else { |
| 111 | + return |
| 112 | + } |
| 113 | + handler() |
| 114 | + } |
| 115 | + } |
| 116 | + |
| 117 | + internal func cancelTimer() { |
| 118 | + currentTask?.cancel() |
| 119 | + currentTask = nil |
| 120 | + } |
| 121 | + |
| 122 | + internal func hasRunningTask() -> Bool { |
| 123 | + currentTask != nil |
| 124 | + } |
| 125 | +} |
| 126 | + |
| 127 | +private final actor ConnectionStatusManager { |
| 128 | + private(set) var status: ConnectionStatus = .disconnected |
| 129 | + private(set) var error: ARTErrorInfo? |
| 130 | + |
| 131 | + internal func updateStatus(to newStatus: ConnectionStatus) { |
| 132 | + status = newStatus |
| 133 | + } |
| 134 | + |
| 135 | + internal func updateError(to newError: ARTErrorInfo?) { |
| 136 | + error = newError |
| 137 | + } |
| 138 | +} |
0 commit comments