Prepare SignalR Hubs for 6.0 (#25447)
Kirk Larkin
GitHub
parent
f98bdf0dc0
commit
294073a200
|
|
@ -12,9 +12,11 @@ uid: signalr/hubs
|
|||
|
||||
# Use hubs in SignalR for ASP.NET Core
|
||||
|
||||
:::moniker range=">= aspnetcore-6.0"
|
||||
|
||||
By [Rachel Appel](https://twitter.com/rachelappel) and [Kevin Griffin](https://twitter.com/1kevgriff)
|
||||
|
||||
[View or download sample code](https://github.com/dotnet/AspNetCore.Docs/tree/main/aspnetcore/signalr/hubs/sample/ ) [(how to download)](xref:index#how-to-download-a-sample)
|
||||
[View or download sample code](https://github.com/dotnet/AspNetCore.Docs/tree/main/aspnetcore/signalr/hubs/samples/) [(how to download)](xref:index#how-to-download-a-sample)
|
||||
|
||||
## What is a SignalR hub
|
||||
|
||||
|
|
@ -22,13 +24,11 @@ The SignalR Hubs API enables you to call methods on connected clients from the s
|
|||
|
||||
## Configure SignalR hubs
|
||||
|
||||
The SignalR middleware requires some services, which are configured by calling `services.AddSignalR`.
|
||||
The SignalR middleware requires some services, which are configured by calling <xref:Microsoft.Extensions.DependencyInjection.SignalRDependencyInjectionExtensions.AddSignalR%2A>:
|
||||
|
||||
[!code-csharp[Configure service](hubs/sample/startup.cs?range=38)]
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Startup.cs" range="38":::
|
||||
|
||||
:::moniker range=">= aspnetcore-3.0"
|
||||
|
||||
When adding SignalR functionality to an ASP.NET Core app, setup SignalR routes by calling `endpoint.MapHub` in the `Startup.Configure` method's `app.UseEndpoints` callback.
|
||||
When adding SignalR functionality to an ASP.NET Core app, setup SignalR routes by calling <xref:Microsoft.AspNetCore.Builder.HubEndpointRouteBuilderExtensions.MapHub%2A> in the `Startup.Configure` method's <xref:Microsoft.AspNetCore.Builder.EndpointRoutingApplicationBuilderExtensions.UseEndpoints%2A> callback:
|
||||
|
||||
```csharp
|
||||
app.UseRouting();
|
||||
|
|
@ -38,19 +38,9 @@ app.UseEndpoints(endpoints =>
|
|||
});
|
||||
```
|
||||
|
||||
:::moniker-end
|
||||
|
||||
:::moniker range="<= aspnetcore-2.2"
|
||||
|
||||
When adding SignalR functionality to an ASP.NET Core app, setup SignalR routes by calling `app.UseSignalR` in the `Startup.Configure` method.
|
||||
|
||||
[!code-csharp[Configure routes to hubs](hubs/sample/startup.cs?range=57-60)]
|
||||
|
||||
:::moniker-end
|
||||
|
||||
## Create and use hubs
|
||||
|
||||
Create a hub by declaring a class that inherits from `Hub`, and add public methods to it. Clients can call methods that are defined as `public`.
|
||||
Create a hub by declaring a class that inherits from <xref:Microsoft.AspNetCore.SignalR.Hub>, and add public methods to it. Clients can call methods that are defined as `public`:
|
||||
|
||||
```csharp
|
||||
public class ChatHub : Hub
|
||||
|
|
@ -72,47 +62,47 @@ You can specify a return type and parameters, including complex types and arrays
|
|||
|
||||
## The Context object
|
||||
|
||||
The `Hub` class has a `Context` property that contains the following properties with information about the connection:
|
||||
The <xref:Microsoft.AspNetCore.SignalR.Hub> class has a <xref:Microsoft.AspNetCore.SignalR.Hub.Context%2A> property that contains the following properties with information about the connection:
|
||||
|
||||
| Property | Description |
|
||||
| ------ | ----------- |
|
||||
| `ConnectionId` | Gets the unique ID for the connection, assigned by SignalR. There is one connection ID for each connection.|
|
||||
| `UserIdentifier` | Gets the [user identifier](xref:signalr/groups). By default, SignalR uses the `ClaimTypes.NameIdentifier` from the `ClaimsPrincipal` associated with the connection as the user identifier. |
|
||||
| `User` | Gets the `ClaimsPrincipal` associated with the current user. |
|
||||
| `Items` | Gets a key/value collection that can be used to share data within the scope of this connection. Data can be stored in this collection and it will persist for the connection across different hub method invocations. |
|
||||
| `Features` | Gets the collection of features available on the connection. For now, this collection isn't needed in most scenarios, so it isn't documented in detail yet. |
|
||||
| `ConnectionAborted` | Gets a `CancellationToken` that notifies when the connection is aborted. |
|
||||
|--|--|
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.ConnectionId%2A> | Gets the unique ID for the connection, assigned by SignalR. There's one connection ID for each connection. |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.UserIdentifier%2A> | Gets the [user identifier](xref:signalr/groups). By default, SignalR uses the <xref:System.Security.Claims.ClaimTypes.NameIdentifier?displayProperty=nameWithType> from the <xref:System.Security.Claims.ClaimsPrincipal> associated with the connection as the user identifier. |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.User%2A> | Gets the <xref:System.Security.Claims.ClaimsPrincipal> associated with the current user. |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.Items%2A> | Gets a key/value collection that can be used to share data within the scope of this connection. Data can be stored in this collection and it will persist for the connection across different hub method invocations. |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.Features%2A> | Gets the collection of features available on the connection. For now, this collection isn't needed in most scenarios, so it isn't documented in detail yet. |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.ConnectionAborted%2A> | Gets a <xref:System.Threading.CancellationToken> that notifies when the connection is aborted. |
|
||||
|
||||
`Hub.Context` also contains the following methods:
|
||||
<xref:Microsoft.AspNetCore.SignalR.Hub.Context%2A?displayProperty=nameWithType> also contains the following methods:
|
||||
|
||||
| Method | Description |
|
||||
| ------ | ----------- |
|
||||
| `GetHttpContext` | Returns the `HttpContext` for the connection, or `null` if the connection is not associated with an HTTP request. For HTTP connections, you can use this method to get information such as HTTP headers and query strings. |
|
||||
| `Abort` | Aborts the connection. |
|
||||
|--|--|
|
||||
| <xref:Microsoft.AspNetCore.SignalR.GetHttpContextExtensions.GetHttpContext%2A> | Returns the <xref:Microsoft.AspNetCore.Http.HttpContext> for the connection, or `null` if the connection isn't associated with an HTTP request. For HTTP connections, you can use this method to get information such as HTTP headers and query strings. |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.Abort%2A> | Aborts the connection. |
|
||||
|
||||
## The Clients object
|
||||
|
||||
The `Hub` class has a `Clients` property that contains the following properties for communication between server and client:
|
||||
The <xref:Microsoft.AspNetCore.SignalR.Hub> class has a <xref:Microsoft.AspNetCore.SignalR.Hub.Clients%2A> property that contains the following properties for communication between server and client:
|
||||
|
||||
| Property | Description |
|
||||
| ------ | ----------- |
|
||||
| `All` | Calls a method on all connected clients |
|
||||
| `Caller` | Calls a method on the client that invoked the hub method |
|
||||
| `Others` | Calls a method on all connected clients except the client that invoked the method |
|
||||
|--|--|
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.All%2A> | Calls a method on all connected clients |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubCallerClients%601.Caller%2A> | Calls a method on the client that invoked the hub method |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubCallerClients%601.Others%2A> | Calls a method on all connected clients except the client that invoked the method |
|
||||
|
||||
`Hub.Clients` also contains the following methods:
|
||||
<xref:Microsoft.AspNetCore.SignalR.Hub.Clients%2A?displayProperty=nameWithType> also contains the following methods:
|
||||
|
||||
| Method | Description |
|
||||
| ------ | ----------- |
|
||||
| `AllExcept` | Calls a method on all connected clients except for the specified connections |
|
||||
| `Client` | Calls a method on a specific connected client |
|
||||
| `Clients` | Calls a method on specific connected clients |
|
||||
| `Group` | Calls a method on all connections in the specified group |
|
||||
| `GroupExcept` | Calls a method on all connections in the specified group, except the specified connections |
|
||||
| `Groups` | Calls a method on multiple groups of connections |
|
||||
| `OthersInGroup` | Calls a method on a group of connections, excluding the client that invoked the hub method |
|
||||
| `User` | Calls a method on all connections associated with a specific user |
|
||||
| `Users` | Calls a method on all connections associated with the specified users |
|
||||
|--|--|
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.AllExcept%2A> | Calls a method on all connected clients except for the specified connections |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.Client%2A> | Calls a method on a specific connected client |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.Clients%2A> | Calls a method on specific connected clients |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.Group%2A> | Calls a method on all connections in the specified group |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.GroupExcept%2A> | Calls a method on all connections in the specified group, except the specified connections |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.Groups%2A> | Calls a method on multiple groups of connections |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubCallerClients%601.OthersInGroup%2A> | Calls a method on a group of connections, excluding the client that invoked the hub method |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.User%2A> | Calls a method on all connections associated with a specific user |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.Users%2A> | Calls a method on all connections associated with the specified users |
|
||||
|
||||
Each property or method in the preceding tables returns an object with a `SendAsync` method. The `SendAsync` method allows you to supply the name and parameters of the client method to call.
|
||||
|
||||
|
|
@ -124,19 +114,19 @@ To make calls to specific clients, use the properties of the `Clients` object. I
|
|||
* `SendMessageToCaller` sends a message back to the caller, using `Clients.Caller`.
|
||||
* `SendMessageToGroup` sends a message to all clients in the `SignalR Users` group.
|
||||
|
||||
[!code-csharp[Send messages](hubs/sample/hubs/chathub.cs?name=HubMethods)]
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/ChatHub.cs" id="HubMethods":::
|
||||
|
||||
## Strongly typed hubs
|
||||
|
||||
A drawback of using `SendAsync` is that it relies on a magic string to specify the client method to be called. This leaves code open to runtime errors if the method name is misspelled or missing from the client.
|
||||
|
||||
An alternative to using `SendAsync` is to strongly type the `Hub` with <xref:Microsoft.AspNetCore.SignalR.Hub%601>. In the following example, the `ChatHub` client methods have been extracted out into an interface called `IChatClient`.
|
||||
An alternative to using `SendAsync` is to strongly type the <xref:Microsoft.AspNetCore.SignalR.Hub> with <xref:Microsoft.AspNetCore.SignalR.Hub%601>. In the following example, the `ChatHub` client methods have been extracted out into an interface called `IChatClient`.
|
||||
|
||||
[!code-csharp[Interface for IChatClient](hubs/sample/hubs/ichatclient.cs?name=snippet_IChatClient)]
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/IChatClient.cs" id="snippet_IChatClient":::
|
||||
|
||||
This interface can be used to refactor the preceding `ChatHub` example.
|
||||
This interface can be used to refactor the preceding `ChatHub` example:
|
||||
|
||||
[!code-csharp[Strongly typed ChatHub](hubs/sample/hubs/StronglyTypedChatHub.cs?range=8-18,36)]
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/StronglyTypedChatHub.cs" range="8-18,36":::
|
||||
|
||||
Using `Hub<IChatClient>` enables compile-time checking of the client methods. This prevents issues caused by using magic strings, since `Hub<T>` can only provide access to the methods defined in the interface.
|
||||
|
||||
|
|
@ -154,27 +144,27 @@ public interface IClient
|
|||
|
||||
## Change the name of a hub method
|
||||
|
||||
By default, a server hub method name is the name of the .NET method. However, you can use the [HubMethodName](xref:Microsoft.AspNetCore.SignalR.HubMethodNameAttribute) attribute to change this default and manually specify a name for the method. The client should use this name, instead of the .NET method name, when invoking the method.
|
||||
By default, a server hub method name is the name of the .NET method. However, you can use the [HubMethodName](xref:Microsoft.AspNetCore.SignalR.HubMethodNameAttribute) attribute to change this default and manually specify a name for the method. The client should use this name, instead of the .NET method name, when invoking the method:
|
||||
|
||||
[!code-csharp[HubMethodName attribute](hubs/sample/hubs/chathub.cs?name=HubMethodName&highlight=1)]
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/ChatHub.cs" id="HubMethodName" highlight="1":::
|
||||
|
||||
## Handle events for a connection
|
||||
|
||||
The SignalR Hubs API provides the `OnConnectedAsync` and `OnDisconnectedAsync` virtual methods to manage and track connections. Override the `OnConnectedAsync` virtual method to perform actions when a client connects to the Hub, such as adding it to a group.
|
||||
The SignalR Hubs API provides the <xref:Microsoft.AspNetCore.SignalR.Hub.OnConnectedAsync%2A> and <xref:Microsoft.AspNetCore.SignalR.Hub.OnDisconnectedAsync%2A> virtual methods to manage and track connections. Override the `OnConnectedAsync` virtual method to perform actions when a client connects to the Hub, such as adding it to a group:
|
||||
|
||||
[!code-csharp[Handle connection](hubs/sample/hubs/chathub.cs?name=OnConnectedAsync)]
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/ChatHub.cs" id="OnConnectedAsync":::
|
||||
|
||||
Override the `OnDisconnectedAsync` virtual method to perform actions when a client disconnects. If the client disconnects intentionally (by calling `connection.stop()`, for example), the `exception` parameter will be `null`. However, if the client is disconnected due to an error (such as a network failure), the `exception` parameter will contain an exception describing the failure.
|
||||
Override the `OnDisconnectedAsync` virtual method to perform actions when a client disconnects. If the client disconnects intentionally (by calling `connection.stop()`, for example), the `exception` parameter will be `null`. However, if the client is disconnected due to an error (such as a network failure), the `exception` parameter will contain an exception describing the failure:
|
||||
|
||||
[!code-csharp[Handle disconnection](hubs/sample/hubs/chathub.cs?name=OnDisconnectedAsync)]
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/ChatHub.cs" id="OnDisconnectedAsync":::
|
||||
|
||||
[!INCLUDE[](~/includes/connectionid-signalr.md)]
|
||||
|
||||
## Handle errors
|
||||
|
||||
Exceptions thrown in your hub methods are sent to the client that invoked the method. On the JavaScript client, the `invoke` method returns a [JavaScript Promise](https://developer.mozilla.org/docs/Web/JavaScript/Guide/Using_promises). When the client receives an error with a handler attached to the promise using `catch`, it's invoked and passed as a JavaScript `Error` object.
|
||||
Exceptions thrown in your hub methods are sent to the client that invoked the method. On the JavaScript client, the `invoke` method returns a [JavaScript Promise](https://developer.mozilla.org/docs/Web/JavaScript/Guide/Using_promises). When the client receives an error with a handler attached to the promise using `catch`, it's invoked and passed as a JavaScript `Error` object:
|
||||
|
||||
[!code-javascript[Error](hubs/sample/wwwroot/js/chat.js?range=23)]
|
||||
:::code language="JavaScript" source="hubs/samples/2.x/SignalRChat/wwwroot/js/chat.js" range="23":::
|
||||
|
||||
If your Hub throws an exception, connections aren't closed. By default, SignalR returns a generic error message to the client. For example:
|
||||
|
||||
|
|
@ -182,11 +172,11 @@ If your Hub throws an exception, connections aren't closed. By default, SignalR
|
|||
Microsoft.AspNetCore.SignalR.HubException: An unexpected error occurred invoking 'MethodName' on the server.
|
||||
```
|
||||
|
||||
Unexpected exceptions often contain sensitive information, such as the name of a database server in an exception triggered when the database connection fails. SignalR doesn't expose these detailed error messages by default as a security measure. See the [Security considerations article](xref:signalr/security#exceptions) for more information on why exception details are suppressed.
|
||||
Unexpected exceptions often contain sensitive information, such as the name of a database server in an exception triggered when the database connection fails. SignalR doesn't expose these detailed error messages by default as a security measure. For more information on why exception details are suppressed, see [Security considerations in ASP.NET Core SignalR](xref:signalr/security#exceptions).
|
||||
|
||||
If you have an exceptional condition you *do* want to propagate to the client, you can use the `HubException` class. If you throw a `HubException` from your hub method, SignalR **will** send the entire message to the client, unmodified.
|
||||
If you have an exceptional condition you *do* want to propagate to the client, you can use the <xref:Microsoft.AspNetCore.SignalR.HubException> class. If you throw a `HubException` from your hub method, SignalR **will** send the entire message to the client, unmodified:
|
||||
|
||||
[!code-csharp[ThrowHubException](hubs/sample/hubs/chathub.cs?name=ThrowHubException&highlight=3)]
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/ChatHub.cs" id="ThrowHubException" highlight="3":::
|
||||
|
||||
> [!NOTE]
|
||||
> SignalR only sends the `Message` property of the exception to the client. The stack trace and other properties on the exception aren't available to the client.
|
||||
|
|
@ -196,3 +186,353 @@ If you have an exceptional condition you *do* want to propagate to the client, y
|
|||
* <xref:signalr/introduction>
|
||||
* <xref:signalr/javascript-client>
|
||||
* <xref:signalr/publish-to-azure-web-app>
|
||||
|
||||
:::moniker-end
|
||||
|
||||
:::moniker range=">= aspnetcore-3.0 < aspnetcore-6.0"
|
||||
|
||||
By [Rachel Appel](https://twitter.com/rachelappel) and [Kevin Griffin](https://twitter.com/1kevgriff)
|
||||
|
||||
[View or download sample code](https://github.com/dotnet/AspNetCore.Docs/tree/main/aspnetcore/signalr/hubs/samples/) [(how to download)](xref:index#how-to-download-a-sample)
|
||||
|
||||
## What is a SignalR hub
|
||||
|
||||
The SignalR Hubs API enables you to call methods on connected clients from the server. In the server code, you define methods that are called by client. In the client code, you define methods that are called from the server. SignalR takes care of everything behind the scenes that makes real-time client-to-server and server-to-client communications possible.
|
||||
|
||||
## Configure SignalR hubs
|
||||
|
||||
The SignalR middleware requires some services, which are configured by calling <xref:Microsoft.Extensions.DependencyInjection.SignalRDependencyInjectionExtensions.AddSignalR%2A>:
|
||||
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Startup.cs" range="38":::
|
||||
|
||||
When adding SignalR functionality to an ASP.NET Core app, setup SignalR routes by calling <xref:Microsoft.AspNetCore.Builder.HubEndpointRouteBuilderExtensions.MapHub%2A> in the `Startup.Configure` method's <xref:Microsoft.AspNetCore.Builder.EndpointRoutingApplicationBuilderExtensions.UseEndpoints%2A> callback:
|
||||
|
||||
```csharp
|
||||
app.UseRouting();
|
||||
app.UseEndpoints(endpoints =>
|
||||
{
|
||||
endpoints.MapHub<ChatHub>("/chathub");
|
||||
});
|
||||
```
|
||||
|
||||
## Create and use hubs
|
||||
|
||||
Create a hub by declaring a class that inherits from <xref:Microsoft.AspNetCore.SignalR.Hub>, and add public methods to it. Clients can call methods that are defined as `public`:
|
||||
|
||||
```csharp
|
||||
public class ChatHub : Hub
|
||||
{
|
||||
public Task SendMessage(string user, string message)
|
||||
{
|
||||
return Clients.All.SendAsync("ReceiveMessage", user, message);
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
You can specify a return type and parameters, including complex types and arrays, as you would in any C# method. SignalR handles the serialization and deserialization of complex objects and arrays in your parameters and return values.
|
||||
|
||||
> [!NOTE]
|
||||
> Hubs are transient:
|
||||
>
|
||||
> * Don't store state in a property on the hub class. Every hub method call is executed on a new hub instance.
|
||||
> * Use `await` when calling asynchronous methods that depend on the hub staying alive. For example, a method such as `Clients.All.SendAsync(...)` can fail if it's called without `await` and the hub method completes before `SendAsync` finishes.
|
||||
|
||||
## The Context object
|
||||
|
||||
The <xref:Microsoft.AspNetCore.SignalR.Hub> class has a <xref:Microsoft.AspNetCore.SignalR.Hub.Context%2A> property that contains the following properties with information about the connection:
|
||||
|
||||
| Property | Description |
|
||||
|--|--|
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.ConnectionId%2A> | Gets the unique ID for the connection, assigned by SignalR. There's one connection ID for each connection. |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.UserIdentifier%2A> | Gets the [user identifier](xref:signalr/groups). By default, SignalR uses the <xref:System.Security.Claims.ClaimTypes.NameIdentifier?displayProperty=nameWithType> from the <xref:System.Security.Claims.ClaimsPrincipal> associated with the connection as the user identifier. |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.User%2A> | Gets the <xref:System.Security.Claims.ClaimsPrincipal> associated with the current user. |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.Items%2A> | Gets a key/value collection that can be used to share data within the scope of this connection. Data can be stored in this collection and it will persist for the connection across different hub method invocations. |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.Features%2A> | Gets the collection of features available on the connection. For now, this collection isn't needed in most scenarios, so it isn't documented in detail yet. |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.ConnectionAborted%2A> | Gets a <xref:System.Threading.CancellationToken> that notifies when the connection is aborted. |
|
||||
|
||||
<xref:Microsoft.AspNetCore.SignalR.Hub.Context%2A?displayProperty=nameWithType> also contains the following methods:
|
||||
|
||||
| Method | Description |
|
||||
|--|--|
|
||||
| <xref:Microsoft.AspNetCore.SignalR.GetHttpContextExtensions.GetHttpContext%2A> | Returns the <xref:Microsoft.AspNetCore.Http.HttpContext> for the connection, or `null` if the connection isn't associated with an HTTP request. For HTTP connections, you can use this method to get information such as HTTP headers and query strings. |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.Abort%2A> | Aborts the connection. |
|
||||
|
||||
## The Clients object
|
||||
|
||||
The <xref:Microsoft.AspNetCore.SignalR.Hub> class has a <xref:Microsoft.AspNetCore.SignalR.Hub.Clients%2A> property that contains the following properties for communication between server and client:
|
||||
|
||||
| Property | Description |
|
||||
|--|--|
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.All%2A> | Calls a method on all connected clients |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubCallerClients%601.Caller%2A> | Calls a method on the client that invoked the hub method |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubCallerClients%601.Others%2A> | Calls a method on all connected clients except the client that invoked the method |
|
||||
|
||||
<xref:Microsoft.AspNetCore.SignalR.Hub.Clients%2A?displayProperty=nameWithType> also contains the following methods:
|
||||
|
||||
| Method | Description |
|
||||
|--|--|
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.AllExcept%2A> | Calls a method on all connected clients except for the specified connections |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.Client%2A> | Calls a method on a specific connected client |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.Clients%2A> | Calls a method on specific connected clients |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.Group%2A> | Calls a method on all connections in the specified group |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.GroupExcept%2A> | Calls a method on all connections in the specified group, except the specified connections |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.Groups%2A> | Calls a method on multiple groups of connections |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubCallerClients%601.OthersInGroup%2A> | Calls a method on a group of connections, excluding the client that invoked the hub method |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.User%2A> | Calls a method on all connections associated with a specific user |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.Users%2A> | Calls a method on all connections associated with the specified users |
|
||||
|
||||
Each property or method in the preceding tables returns an object with a `SendAsync` method. The `SendAsync` method allows you to supply the name and parameters of the client method to call.
|
||||
|
||||
## Send messages to clients
|
||||
|
||||
To make calls to specific clients, use the properties of the `Clients` object. In the following example, there are three Hub methods:
|
||||
|
||||
* `SendMessage` sends a message to all connected clients, using `Clients.All`.
|
||||
* `SendMessageToCaller` sends a message back to the caller, using `Clients.Caller`.
|
||||
* `SendMessageToGroup` sends a message to all clients in the `SignalR Users` group.
|
||||
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/ChatHub.cs" id="HubMethods":::
|
||||
|
||||
## Strongly typed hubs
|
||||
|
||||
A drawback of using `SendAsync` is that it relies on a magic string to specify the client method to be called. This leaves code open to runtime errors if the method name is misspelled or missing from the client.
|
||||
|
||||
An alternative to using `SendAsync` is to strongly type the <xref:Microsoft.AspNetCore.SignalR.Hub> with <xref:Microsoft.AspNetCore.SignalR.Hub%601>. In the following example, the `ChatHub` client methods have been extracted out into an interface called `IChatClient`.
|
||||
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/IChatClient.cs" id="snippet_IChatClient":::
|
||||
|
||||
This interface can be used to refactor the preceding `ChatHub` example:
|
||||
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/StronglyTypedChatHub.cs" range="8-18,36":::
|
||||
|
||||
Using `Hub<IChatClient>` enables compile-time checking of the client methods. This prevents issues caused by using magic strings, since `Hub<T>` can only provide access to the methods defined in the interface.
|
||||
|
||||
Using a strongly typed `Hub<T>` disables the ability to use `SendAsync`. Any methods defined on the interface can still be defined as asynchronous. In fact, each of these methods should return a `Task`. Since it's an interface, don't use the `async` keyword. For example:
|
||||
|
||||
```csharp
|
||||
public interface IClient
|
||||
{
|
||||
Task ClientMethod();
|
||||
}
|
||||
```
|
||||
|
||||
> [!NOTE]
|
||||
> The `Async` suffix isn't stripped from the method name. Unless your client method is defined with `.on('MyMethodAsync')`, you shouldn't use `MyMethodAsync` as a name.
|
||||
|
||||
## Change the name of a hub method
|
||||
|
||||
By default, a server hub method name is the name of the .NET method. However, you can use the [HubMethodName](xref:Microsoft.AspNetCore.SignalR.HubMethodNameAttribute) attribute to change this default and manually specify a name for the method. The client should use this name, instead of the .NET method name, when invoking the method:
|
||||
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/ChatHub.cs" id="HubMethodName" highlight="1":::
|
||||
|
||||
## Handle events for a connection
|
||||
|
||||
The SignalR Hubs API provides the <xref:Microsoft.AspNetCore.SignalR.Hub.OnConnectedAsync%2A> and <xref:Microsoft.AspNetCore.SignalR.Hub.OnDisconnectedAsync%2A> virtual methods to manage and track connections. Override the `OnConnectedAsync` virtual method to perform actions when a client connects to the Hub, such as adding it to a group:
|
||||
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/ChatHub.cs" id="OnConnectedAsync":::
|
||||
|
||||
Override the `OnDisconnectedAsync` virtual method to perform actions when a client disconnects. If the client disconnects intentionally (by calling `connection.stop()`, for example), the `exception` parameter will be `null`. However, if the client is disconnected due to an error (such as a network failure), the `exception` parameter will contain an exception describing the failure:
|
||||
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/ChatHub.cs" id="OnDisconnectedAsync":::
|
||||
|
||||
[!INCLUDE[](~/includes/connectionid-signalr.md)]
|
||||
|
||||
## Handle errors
|
||||
|
||||
Exceptions thrown in your hub methods are sent to the client that invoked the method. On the JavaScript client, the `invoke` method returns a [JavaScript Promise](https://developer.mozilla.org/docs/Web/JavaScript/Guide/Using_promises). When the client receives an error with a handler attached to the promise using `catch`, it's invoked and passed as a JavaScript `Error` object:
|
||||
|
||||
:::code language="JavaScript" source="hubs/samples/2.x/SignalRChat/wwwroot/js/chat.js" range="23":::
|
||||
|
||||
If your Hub throws an exception, connections aren't closed. By default, SignalR returns a generic error message to the client. For example:
|
||||
|
||||
```
|
||||
Microsoft.AspNetCore.SignalR.HubException: An unexpected error occurred invoking 'MethodName' on the server.
|
||||
```
|
||||
|
||||
Unexpected exceptions often contain sensitive information, such as the name of a database server in an exception triggered when the database connection fails. SignalR doesn't expose these detailed error messages by default as a security measure. For more information on why exception details are suppressed, see [Security considerations in ASP.NET Core SignalR](xref:signalr/security#exceptions).
|
||||
|
||||
If you have an exceptional condition you *do* want to propagate to the client, you can use the <xref:Microsoft.AspNetCore.SignalR.HubException> class. If you throw a `HubException` from your hub method, SignalR **will** send the entire message to the client, unmodified:
|
||||
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/ChatHub.cs" id="ThrowHubException" highlight="3":::
|
||||
|
||||
> [!NOTE]
|
||||
> SignalR only sends the `Message` property of the exception to the client. The stack trace and other properties on the exception aren't available to the client.
|
||||
|
||||
## Additional resources
|
||||
|
||||
* <xref:signalr/introduction>
|
||||
* <xref:signalr/javascript-client>
|
||||
* <xref:signalr/publish-to-azure-web-app>
|
||||
|
||||
:::moniker-end
|
||||
|
||||
:::moniker range="< aspnetcore-3.0"
|
||||
|
||||
By [Rachel Appel](https://twitter.com/rachelappel) and [Kevin Griffin](https://twitter.com/1kevgriff)
|
||||
|
||||
[View or download sample code](https://github.com/dotnet/AspNetCore.Docs/tree/main/aspnetcore/signalr/hubs/samples/) [(how to download)](xref:index#how-to-download-a-sample)
|
||||
|
||||
## What is a SignalR hub
|
||||
|
||||
The SignalR Hubs API enables you to call methods on connected clients from the server. In the server code, you define methods that are called by client. In the client code, you define methods that are called from the server. SignalR takes care of everything behind the scenes that makes real-time client-to-server and server-to-client communications possible.
|
||||
|
||||
## Configure SignalR hubs
|
||||
|
||||
The SignalR middleware requires some services, which are configured by calling <xref:Microsoft.Extensions.DependencyInjection.SignalRDependencyInjectionExtensions.AddSignalR%2A>:
|
||||
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Startup.cs" range="38":::
|
||||
|
||||
When adding SignalR functionality to an ASP.NET Core app, setup SignalR routes by calling <xref:Microsoft.AspNetCore.Builder.SignalRAppBuilderExtensions.UseSignalR%2A> in the `Startup.Configure` method:
|
||||
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Startup.cs" range="57-60":::
|
||||
|
||||
## Create and use hubs
|
||||
|
||||
Create a hub by declaring a class that inherits from <xref:Microsoft.AspNetCore.SignalR.Hub>, and add public methods to it. Clients can call methods that are defined as `public`:
|
||||
|
||||
```csharp
|
||||
public class ChatHub : Hub
|
||||
{
|
||||
public Task SendMessage(string user, string message)
|
||||
{
|
||||
return Clients.All.SendAsync("ReceiveMessage", user, message);
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
You can specify a return type and parameters, including complex types and arrays, as you would in any C# method. SignalR handles the serialization and deserialization of complex objects and arrays in your parameters and return values.
|
||||
|
||||
> [!NOTE]
|
||||
> Hubs are transient:
|
||||
>
|
||||
> * Don't store state in a property on the hub class. Every hub method call is executed on a new hub instance.
|
||||
> * Use `await` when calling asynchronous methods that depend on the hub staying alive. For example, a method such as `Clients.All.SendAsync(...)` can fail if it's called without `await` and the hub method completes before `SendAsync` finishes.
|
||||
|
||||
## The Context object
|
||||
|
||||
The <xref:Microsoft.AspNetCore.SignalR.Hub> class has a <xref:Microsoft.AspNetCore.SignalR.Hub.Context%2A> property that contains the following properties with information about the connection:
|
||||
|
||||
| Property | Description |
|
||||
|--|--|
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.ConnectionId%2A> | Gets the unique ID for the connection, assigned by SignalR. There's one connection ID for each connection. |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.UserIdentifier%2A> | Gets the [user identifier](xref:signalr/groups). By default, SignalR uses the <xref:System.Security.Claims.ClaimTypes.NameIdentifier?displayProperty=nameWithType> from the <xref:System.Security.Claims.ClaimsPrincipal> associated with the connection as the user identifier. |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.User%2A> | Gets the <xref:System.Security.Claims.ClaimsPrincipal> associated with the current user. |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.Items%2A> | Gets a key/value collection that can be used to share data within the scope of this connection. Data can be stored in this collection and it will persist for the connection across different hub method invocations. |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.Features%2A> | Gets the collection of features available on the connection. For now, this collection isn't needed in most scenarios, so it isn't documented in detail yet. |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.ConnectionAborted%2A> | Gets a <xref:System.Threading.CancellationToken> that notifies when the connection is aborted. |
|
||||
|
||||
<xref:Microsoft.AspNetCore.SignalR.Hub.Context%2A?displayProperty=nameWithType> also contains the following methods:
|
||||
|
||||
| Method | Description |
|
||||
|--|--|
|
||||
| <xref:Microsoft.AspNetCore.SignalR.GetHttpContextExtensions.GetHttpContext%2A> | Returns the <xref:Microsoft.AspNetCore.Http.HttpContext> for the connection, or `null` if the connection isn't associated with an HTTP request. For HTTP connections, you can use this method to get information such as HTTP headers and query strings. |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.HubCallerContext.Abort%2A> | Aborts the connection. |
|
||||
|
||||
## The Clients object
|
||||
|
||||
The <xref:Microsoft.AspNetCore.SignalR.Hub> class has a <xref:Microsoft.AspNetCore.SignalR.Hub.Clients%2A> property that contains the following properties for communication between server and client:
|
||||
|
||||
| Property | Description |
|
||||
|--|--|
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.All%2A> | Calls a method on all connected clients |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubCallerClients%601.Caller%2A> | Calls a method on the client that invoked the hub method |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubCallerClients%601.Others%2A> | Calls a method on all connected clients except the client that invoked the method |
|
||||
|
||||
<xref:Microsoft.AspNetCore.SignalR.Hub.Clients%2A?displayProperty=nameWithType> also contains the following methods:
|
||||
|
||||
| Method | Description |
|
||||
|--|--|
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.AllExcept%2A> | Calls a method on all connected clients except for the specified connections |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.Client%2A> | Calls a method on a specific connected client |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.Clients%2A> | Calls a method on specific connected clients |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.Group%2A> | Calls a method on all connections in the specified group |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.GroupExcept%2A> | Calls a method on all connections in the specified group, except the specified connections |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.Groups%2A> | Calls a method on multiple groups of connections |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubCallerClients%601.OthersInGroup%2A> | Calls a method on a group of connections, excluding the client that invoked the hub method |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.User%2A> | Calls a method on all connections associated with a specific user |
|
||||
| <xref:Microsoft.AspNetCore.SignalR.IHubClients%601.Users%2A> | Calls a method on all connections associated with the specified users |
|
||||
|
||||
Each property or method in the preceding tables returns an object with a `SendAsync` method. The `SendAsync` method allows you to supply the name and parameters of the client method to call.
|
||||
|
||||
## Send messages to clients
|
||||
|
||||
To make calls to specific clients, use the properties of the `Clients` object. In the following example, there are three Hub methods:
|
||||
|
||||
* `SendMessage` sends a message to all connected clients, using `Clients.All`.
|
||||
* `SendMessageToCaller` sends a message back to the caller, using `Clients.Caller`.
|
||||
* `SendMessageToGroup` sends a message to all clients in the `SignalR Users` group.
|
||||
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/ChatHub.cs" id="HubMethods":::
|
||||
|
||||
## Strongly typed hubs
|
||||
|
||||
A drawback of using `SendAsync` is that it relies on a magic string to specify the client method to be called. This leaves code open to runtime errors if the method name is misspelled or missing from the client.
|
||||
|
||||
An alternative to using `SendAsync` is to strongly type the <xref:Microsoft.AspNetCore.SignalR.Hub> with <xref:Microsoft.AspNetCore.SignalR.Hub%601>. In the following example, the `ChatHub` client methods have been extracted out into an interface called `IChatClient`.
|
||||
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/IChatClient.cs" id="snippet_IChatClient":::
|
||||
|
||||
This interface can be used to refactor the preceding `ChatHub` example:
|
||||
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/StronglyTypedChatHub.cs" range="8-18,36":::
|
||||
|
||||
Using `Hub<IChatClient>` enables compile-time checking of the client methods. This prevents issues caused by using magic strings, since `Hub<T>` can only provide access to the methods defined in the interface.
|
||||
|
||||
Using a strongly typed `Hub<T>` disables the ability to use `SendAsync`. Any methods defined on the interface can still be defined as asynchronous. In fact, each of these methods should return a `Task`. Since it's an interface, don't use the `async` keyword. For example:
|
||||
|
||||
```csharp
|
||||
public interface IClient
|
||||
{
|
||||
Task ClientMethod();
|
||||
}
|
||||
```
|
||||
|
||||
> [!NOTE]
|
||||
> The `Async` suffix isn't stripped from the method name. Unless your client method is defined with `.on('MyMethodAsync')`, you shouldn't use `MyMethodAsync` as a name.
|
||||
|
||||
## Change the name of a hub method
|
||||
|
||||
By default, a server hub method name is the name of the .NET method. However, you can use the [HubMethodName](xref:Microsoft.AspNetCore.SignalR.HubMethodNameAttribute) attribute to change this default and manually specify a name for the method. The client should use this name, instead of the .NET method name, when invoking the method:
|
||||
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/ChatHub.cs" id="HubMethodName" highlight="1":::
|
||||
|
||||
## Handle events for a connection
|
||||
|
||||
The SignalR Hubs API provides the <xref:Microsoft.AspNetCore.SignalR.Hub.OnConnectedAsync%2A> and <xref:Microsoft.AspNetCore.SignalR.Hub.OnDisconnectedAsync%2A> virtual methods to manage and track connections. Override the `OnConnectedAsync` virtual method to perform actions when a client connects to the Hub, such as adding it to a group:
|
||||
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/ChatHub.cs" id="OnConnectedAsync":::
|
||||
|
||||
Override the `OnDisconnectedAsync` virtual method to perform actions when a client disconnects. If the client disconnects intentionally (by calling `connection.stop()`, for example), the `exception` parameter will be `null`. However, if the client is disconnected due to an error (such as a network failure), the `exception` parameter will contain an exception describing the failure:
|
||||
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/ChatHub.cs" id="OnDisconnectedAsync":::
|
||||
|
||||
[!INCLUDE[](~/includes/connectionid-signalr.md)]
|
||||
|
||||
## Handle errors
|
||||
|
||||
Exceptions thrown in your hub methods are sent to the client that invoked the method. On the JavaScript client, the `invoke` method returns a [JavaScript Promise](https://developer.mozilla.org/docs/Web/JavaScript/Guide/Using_promises). When the client receives an error with a handler attached to the promise using `catch`, it's invoked and passed as a JavaScript `Error` object:
|
||||
|
||||
:::code language="JavaScript" source="hubs/samples/2.x/SignalRChat/wwwroot/js/chat.js" range="23":::
|
||||
|
||||
If your Hub throws an exception, connections aren't closed. By default, SignalR returns a generic error message to the client. For example:
|
||||
|
||||
```
|
||||
Microsoft.AspNetCore.SignalR.HubException: An unexpected error occurred invoking 'MethodName' on the server.
|
||||
```
|
||||
|
||||
Unexpected exceptions often contain sensitive information, such as the name of a database server in an exception triggered when the database connection fails. SignalR doesn't expose these detailed error messages by default as a security measure. For more information on why exception details are suppressed, see [Security considerations in ASP.NET Core SignalR](xref:signalr/security#exceptions).
|
||||
|
||||
If you have an exceptional condition you *do* want to propagate to the client, you can use the <xref:Microsoft.AspNetCore.SignalR.HubException> class. If you throw a `HubException` from your hub method, SignalR **will** send the entire message to the client, unmodified:
|
||||
|
||||
:::code language="csharp" source="hubs/samples/2.x/SignalRChat/Hubs/ChatHub.cs" id="ThrowHubException" highlight="3":::
|
||||
|
||||
> [!NOTE]
|
||||
> SignalR only sends the `Message` property of the exception to the client. The stack trace and other properties on the exception aren't available to the client.
|
||||
|
||||
## Additional resources
|
||||
|
||||
* <xref:signalr/introduction>
|
||||
* <xref:signalr/javascript-client>
|
||||
* <xref:signalr/publish-to-azure-web-app>
|
||||
|
||||
:::moniker-end
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ namespace SignalRChat.Hubs
|
|||
{
|
||||
public class ChatHub : Hub
|
||||
{
|
||||
#region HubMethods
|
||||
// <HubMethods>
|
||||
public Task SendMessage(string user, string message)
|
||||
{
|
||||
return Clients.All.SendAsync("ReceiveMessage", user, message);
|
||||
|
|
@ -22,37 +22,37 @@ namespace SignalRChat.Hubs
|
|||
{
|
||||
return Clients.Group("SignalR Users").SendAsync("ReceiveMessage", user, message);
|
||||
}
|
||||
#endregion
|
||||
// </HubMethods>
|
||||
|
||||
#region HubMethodName
|
||||
// <HubMethodName>
|
||||
[HubMethodName("SendMessageToUser")]
|
||||
public Task DirectMessage(string user, string message)
|
||||
{
|
||||
return Clients.User(user).SendAsync("ReceiveMessage", user, message);
|
||||
}
|
||||
#endregion
|
||||
// </HubMethodName>
|
||||
|
||||
#region ThrowHubException
|
||||
// <ThrowHubException>
|
||||
public Task ThrowException()
|
||||
{
|
||||
throw new HubException("This error will be sent to the client!");
|
||||
}
|
||||
#endregion
|
||||
// </ThrowHubException>
|
||||
|
||||
#region OnConnectedAsync
|
||||
// <OnConnectedAsync>
|
||||
public override async Task OnConnectedAsync()
|
||||
{
|
||||
await Groups.AddToGroupAsync(Context.ConnectionId, "SignalR Users");
|
||||
await base.OnConnectedAsync();
|
||||
}
|
||||
#endregion
|
||||
// </OnConnectedAsync>
|
||||
|
||||
#region OnDisconnectedAsync
|
||||
// <OnDisconnectedAsync>
|
||||
public override async Task OnDisconnectedAsync(Exception exception)
|
||||
{
|
||||
await Groups.RemoveFromGroupAsync(Context.ConnectionId, "SignalR Users");
|
||||
await base.OnDisconnectedAsync(exception);
|
||||
}
|
||||
#endregion
|
||||
// </OnDisconnectedAsync>
|
||||
}
|
||||
}
|
||||
|
|
@ -2,10 +2,10 @@ using System.Threading.Tasks;
|
|||
|
||||
namespace SignalRChat.Hubs
|
||||
{
|
||||
#region snippet_IChatClient
|
||||
// <snippet_IChatClient>
|
||||
public interface IChatClient
|
||||
{
|
||||
Task ReceiveMessage(string user, string message);
|
||||
}
|
||||
#endregion
|
||||
// </snippet_IChatClient>
|
||||
}
|
||||
|
Before Width: | Height: | Size: 31 KiB After Width: | Height: | Size: 31 KiB |
|
Before Width: | Height: | Size: 9.5 KiB After Width: | Height: | Size: 9.5 KiB |
|
Before Width: | Height: | Size: 8.2 KiB After Width: | Height: | Size: 8.2 KiB |
|
Before Width: | Height: | Size: 12 KiB After Width: | Height: | Size: 12 KiB |
Loading…
Reference in New Issue