Update introduction.md (#23328)
* Update introduction.md Correct the introduction phrasing of RPC calls, it is not always JavaScript - that is but a single client SDK. * Update introduction.md * Apply suggestions from code reviewpull/23332/head
parent
e5c703659d
commit
8788617b25
|
@ -5,7 +5,7 @@ description: Learn how the ASP.NET Core SignalR library simplifies adding real-t
|
|||
monikerRange: '>= aspnetcore-2.1'
|
||||
ms.author: bradyg
|
||||
ms.custom: mvc
|
||||
ms.date: 11/27/2019
|
||||
ms.date: 9/16/2021
|
||||
no-loc: [Home, Privacy, Kestrel, appsettings.json, "ASP.NET Core Identity", cookie, Cookie, Blazor, "Blazor Server", "Blazor WebAssembly", "Identity", "Let's Encrypt", Razor, SignalR]
|
||||
uid: signalr/introduction
|
||||
---
|
||||
|
@ -22,7 +22,7 @@ Good candidates for SignalR:
|
|||
* Collaborative apps. Whiteboard apps and team meeting software are examples of collaborative apps.
|
||||
* Apps that require notifications. Social networks, email, chat, games, travel alerts, and many other apps use notifications.
|
||||
|
||||
SignalR provides an API for creating server-to-client [remote procedure calls (RPC)](https://wikipedia.org/wiki/Remote_procedure_call). The RPCs call JavaScript functions on clients from server-side .NET Core code.
|
||||
SignalR provides an API for creating server-to-client [remote procedure calls (RPC)](https://wikipedia.org/wiki/Remote_procedure_call). The RPCs invoke functions on clients from server-side .NET Core code. There are several [supported platforms](xref:signalr/supported-platforms), each with their respective client SDK. Because of this, the programming language being invoked by the RPC call varies.
|
||||
|
||||
Here are some features of SignalR for ASP.NET Core:
|
||||
|
||||
|
|
Loading…
Reference in New Issue