Some more updates

Author: zackliu

aspnetcore/signalr/client-features.md

@@ -29,18 +29,18 @@ The 1.x versions of SignalR map to the 2.1 and 2.2 .NET Core releases and have t
 
 The table below shows the features and support for the clients that offer real-time support. For each feature, the *minimum* version supporting this feature is listed. If no version is listed, the feature isn't supported.
 
-| Feature | Server | .NET client | JavaScript client | Java client |
-| ---- | :-: | :-: | :-: | :-: |
-| Azure SignalR Service Support |2.1.0|1.0.0|1.0.0|1.0.0|
-| [Server-to-client Streaming](xref:signalr/streaming)          |2.1.0|1.0.0|1.0.0|1.0.0|
-| [Client-to-server Streaming](xref:signalr/streaming)          |3.0.0|3.0.0|3.0.0|3.0.0|
-| Automatic Reconnection ([.NET](xref:signalr/dotnet-client#handle-lost-connection), [JavaScript](xref:signalr/javascript-client#reconnect-clients))          |3.0.0|3.0.0|3.0.0|❌|
-| WebSockets Transport |2.1.0|1.0.0|1.0.0|1.0.0|
-| Server-Sent Events Transport |2.1.0|1.0.0|1.0.0|❌|
-| Long Polling Transport |2.1.0|1.0.0|1.0.0|3.0.0|
-| JSON Hub Protocol |2.1.0|1.0.0|1.0.0|1.0.0|
-| MessagePack Hub Protocol |2.1.0|1.0.0|1.0.0|5.0.0|
-| Client Results |7.0.0|7.0.0|7.0.0|7.0.0|
+| Feature | Server | .NET client | JavaScript client | Java client | Swift client |
+| ---- | :-: | :-: | :-: | :-: | :-: |
+| Azure SignalR Service Support |2.1.0|1.0.0|1.0.0|1.0.0|1.0.0-preview.1|
+| [Server-to-client Streaming](xref:signalr/streaming)          |2.1.0|1.0.0|1.0.0|1.0.0|1.0.0-preview.1|
+| [Client-to-server Streaming](xref:signalr/streaming)          |3.0.0|3.0.0|3.0.0|3.0.0|❌|
+| Automatic Reconnection ([.NET](xref:signalr/dotnet-client#handle-lost-connection), [JavaScript](xref:signalr/javascript-client#reconnect-clients))          |3.0.0|3.0.0|3.0.0|❌|1.0.0-preview.1|
+| WebSockets Transport |2.1.0|1.0.0|1.0.0|1.0.0|1.0.0-preview.1|
+| Server-Sent Events Transport |2.1.0|1.0.0|1.0.0|❌|1.0.0-preview.1|
+| Long Polling Transport |2.1.0|1.0.0|1.0.0|3.0.0|1.0.0-preview.1|
+| JSON Hub Protocol |2.1.0|1.0.0|1.0.0|1.0.0|1.0.0-preview.1|
+| MessagePack Hub Protocol |2.1.0|1.0.0|1.0.0|5.0.0|1.0.0-preview.1|
+| Client Results |7.0.0|7.0.0|7.0.0|7.0.0|1.0.0-preview.1|
 
 Support for enabling additional client features is tracked in [our issue tracker](https://github.com/dotnet/AspNetCore/issues).
 

aspnetcore/signalr/swift-client.md

@@ -32,15 +32,10 @@ import PackageDescription
 let package = Package(
     name: "signalr-client-app",
     dependencies: [
-        .package(url: "https://github.com/Azure/signalr-swift")
+        .package(url: "https://github.com/dotnet/signalr-client-swift", branch: "main")
     ],
     targets: [
-        .target(
-            name: "YourTargetName",
-            dependencies: [
-                .product(name: "SignalRClient", package: "signalr-swift")
-            ]
-        )
+        .executableTarget(name: "YourTargetName", dependencies: [.product(name: "SignalRClient", package: "signalr-client-swift")])
     ]
 )
 ```
@@ -175,6 +170,22 @@ let connection = HubConnectionBuilder()
 
 Without parameters, withAutomaticReconnect() configures the client to wait 0, 2, 10, and 30 seconds respectively before each reconnect attempt. After four failed attempts, the client stops trying to reconnect.
 
+Before starting any reconnect attempts, the `HubConnection` transitions to the `Reconnecting` state and fires its `onReconnecting` callbacks.
+
+After the reconnection succeeds, the `HubConnection` transitions to the `connected` state and fires its `onReconnected` callbacks.
+
+A general way to use `onReconnecting` and `onReconnected` is to mark the connection state changes:
+
+```swift
+connection.onReconnecting { error in
+    // connection is disconnected because of error
+}
+
+connection.onReconnected {
+    // connection is connected back
+}
+```
+
 ### Configure strategy in automatic reconnect
 
 To customize the reconnect behavior, you can pass an array of numbers representing the delay in seconds before each reconnect attempt. For more granular control, pass an object that conforms to the RetryPolicy protocol.
@@ -216,6 +227,22 @@ You can customize the client's timeout and keep-alive settings via the HubConnec
 |withKeepAliveInterval| 15 (seconds)|Determines the interval at which the client sends ping messages and is set directly on HubConnectionBuilder. This setting allows the server to detect hard disconnects, such as when a client unplugs their computer from the network. Sending any message from the client resets the timer to the start of the interval. If the client hasn't sent a message in the ClientTimeoutInterval set on the server, the server considers the client disconnected.|
 |withServerTimeout| 30 (seconds)|Determines the interval at which the client waits for a response from the server before it considers the server disconnected. This setting is set directly on HubConnectionBuilder.|
 
+## Configure transport
+
+The SignalR Swift client supports three transports: LongPolling, ServerSentEvents, and WebSockets. By default, the client will use WebSockets if the server supports it, and fall back to ServerSentEvents and LongPolling if it doesn't. You can configure the client to use a specific transport by calling `withUrl(url:transport:)` while building the connection.
+
+```swift
+let connection = HubConnectionBuilder()
+    .withUrl(url: "https://your-signalr-server", transport: .webSockets) // use websocket only
+    .build()
+```
+
+```swift
+let connection = HubConnectionBuilder()
+    .withUrl(url: "https://your-signalr-server", transport: [.webSockets, .serverSentEvents]) // use websockets and server sent events
+    .build()
+```
+
 ## Additional resources
 
 * [WebPack and TypeScript tutorial](xref:tutorials/signalr-typescript-webpack)