-
Notifications
You must be signed in to change notification settings - Fork 10.7k
Expose ConnectionId on SignalR Clients #8681
Copy link
Copy link
Closed
Labels
DoneThis issue has been fixedThis issue has been fixedacceptedThis issue has completed "acceptance" testing (including accessibility)This issue has completed "acceptance" testing (including accessibility)area-signalrIncludes: SignalR clients and serversIncludes: SignalR clients and serversfeature-client-javaRelated to the SignalR Java clientRelated to the SignalR Java clientfeature-client-javascriptRelated to the SignalR JS clientRelated to the SignalR JS clientfeature-client-netRelated to the SignalR .NET clientRelated to the SignalR .NET client
Milestone
Metadata
Metadata
Assignees
Labels
DoneThis issue has been fixedThis issue has been fixedacceptedThis issue has completed "acceptance" testing (including accessibility)This issue has completed "acceptance" testing (including accessibility)area-signalrIncludes: SignalR clients and serversIncludes: SignalR clients and serversfeature-client-javaRelated to the SignalR Java clientRelated to the SignalR Java clientfeature-client-javascriptRelated to the SignalR JS clientRelated to the SignalR JS clientfeature-client-netRelated to the SignalR .NET clientRelated to the SignalR .NET client
Type
Fields
Give feedbackNo fields configured for issues without a type.
We've had users ask about how to get a client's connectionId Our current guidance to users on how to get it is to create a Hub method to return it to them e.g.
Which is less than ideal.
Another thing we planned on doing for the
onReconnectedevents is making it have a single parameter which would be the client's new connectionId.