* SignalR: Reference shared framework
* Update aspnetcore/signalr/hubs.md
Committing the inline suggestion, and then will update the missing link afterwards.
Co-authored-by: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
* Moved 7.0 version up, moved new note to bottom of topics
* Removed dupe.
* added note in 5 more topics, moved latest versions to top where needed
* New include, reduced number of topics, added resources links
* Moved link in migration doc to internal.
* Added description for xref since subsection title not generated
* Removed note from hubcontext, using additional resources link now
* Reduced new section in migration topic per Rick suggestion
* Apply suggestions from code review
Added additional suggestions to link.
Co-authored-by: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
* Moved note back to near top of hubs.md all 3 versions per Brennan suggestion
---------
Co-authored-by: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
* Update hubs.md
Make it clear that Hubs should not be created directly.
* Updates
* Update hubs.md
Improved wording.
---------
Co-authored-by: Luke Latham <1622880+guardrex@users.noreply.github.com>
* No need to explicitly call RemoveFromGroupAsync
The sample added this explicit `RemoveFromGroupAsync` call when the connection disconnects, however, it is a redundant call since when the connection disconnects, it is automatically removed from the group.
We have customers using Azure SignalR followed this sample and invokes `RemoveFromGroupAsync` for every client disconnect, this increases unnecessary burdon to the Azure SignalR service when the client connection closes burst.
* Update hubs.md
Section Handle events for a connection for all versions: Noted no need for RemoveFromGroupAsync in OnConnectedAsync
* Update hubs.md
Added note on RemoveFromGroupsAsync to all versions of topic. Corrected Typo.
* Update aspnetcore/signalr/hubs.md
Improved statement.
Co-authored-by: Brennan <brecon@microsoft.com>
* Update hubs.md
Updated statement on RemoveFromGroupAsync for all topic versions.
* Update gRPC example for StronglyTypedChatHubs.cs
Removed RemoveFromGroupAsync call from OnDisconnectedAsync.
Co-authored-by: Wade Pickett <wpickett@microsoft.com>
Co-authored-by: Brennan <brecon@microsoft.com>
* New include connectID security warning & applied to hubs.md for SignalR
* patch: Corrected grammar on include warning.
* patch: adding ConnectID section to security.md for Signalr.
* Update aspnetcore/includes/connectionid-signalr.md
Co-Authored-By: Stephen Halter <halter73@gmail.com>
* Update security.md
Changed "ConnectionID" to "ConnectionId"
Co-authored-by: Stephen Halter <halter73@gmail.com>
* Clarify use of async in strongly typed Hub
* Update aspnetcore/signalr/hubs.md
Co-Authored-By: scottaddie <10702007+scottaddie@users.noreply.github.com>
* React to feedback
* overview
* whats new to end
* fix migration node
* split fundamentals, move to end
* glob & loc, get started
* security node name
* security section
* azure, client-side, host
* several more sections
* redistribute tutorials
* proofread fixes
* move how to download section
* index files delete and redirect
* fix errors
* reorder some nodes
* scott feedback, flatten main tutorials node
* fix missed feedback items + other issues
* unflatten tutorials node
* move 'how to download'
* more tutorials node tweaks
* standardize view sample links
* db --> DB
* fix build error
* remove link from a parent node
* streamline node names
* xref links
* typos
* typo
* typos and revert some xref links
* scott feedback
* scott feedback
* feedback
* change node name
* safe storage-->protect
Fixes#8505
Added the section to signalr/hubs.md for Hub<T>. Added a refactored version of `ChatHub` to use an interface instead of `SendAsync`.
Any feedback is greatly appreciated! My first PR to docs!
* Those methods are not defined at the Hub class
The methods below aren't defined at the Hub class but accessible through Clients property like the first three properties (All, Caller, Others) :
| `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` | Sends a message to all connections in the specified group |
| `GroupExcept` | Sends a message to all connections in the specified group, except the specified connections |
| `Groups` | Sends a message to multiple groups of connections |
| `OthersInGroup` | Sends a message to a group of connections, excluding the client that invoked the hub method |
| `User` | Sends a message to all connections associated with a specific user |
| `Users` | Sends a message to all connections associated with the specified users |
So I think it might good to move all those methods description to the first table whic talk about `Clients` property.
* Update hubs.md
Revert to two tables but, for the second table, we specify where the methods come from `Hub.Clients` property.