Skip to content

Expose ConnectionId on SignalR Clients #8681

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
3 tasks done
mikaelm12 opened this issue Mar 20, 2019 · 1 comment
Closed
3 tasks done

Expose ConnectionId on SignalR Clients #8681

mikaelm12 opened this issue Mar 20, 2019 · 1 comment
Assignees
@mikaelm12
Labels
accepted This issue has completed "acceptance" testing (including accessibility) area-signalr Includes: SignalR clients and servers Done This issue has been fixed feature-client-java Related to the SignalR Java client feature-client-javascript Related to the SignalR JS client feature-client-net Related to the SignalR .NET client
Milestone
3.0.0-preview4

Comments

@mikaelm12
Copy link
Contributor

mikaelm12 commented Mar 20, 2019 •
edited
Loading

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.

public string GetConnectionId() 
{
    return Context.ConnectionId
}

Which is less than ideal.

Another thing we planned on doing for the onReconnected events is making it have a single parameter which would be the client's new connectionId.

  • .NET
  • Java
  • JavaScript
@mikaelm12 mikaelm12 added area-signalr Includes: SignalR clients and servers feature-client-java Related to the SignalR Java client feature-client-net Related to the SignalR .NET client feature-client-javascript Related to the SignalR JS client labels Mar 20, 2019
@mikaelm12 mikaelm12 mentioned this issue Mar 20, 2019
Merged
@halter73 halter73 added this to the 3.0.0-preview4 milestone Mar 25, 2019
@halter73 halter73 mentioned this issue Mar 26, 2019
Closed
@mikaelm12 mikaelm12 mentioned this issue Mar 26, 2019
Merged
@analogrelay
Copy link
Contributor

Still have JavaScript to do here right? Is this going to land for preview 4 (end of this week)?

@mikaelm12 mikaelm12 mentioned this issue Apr 9, 2019
Merged
@analogrelay analogrelay mentioned this issue Apr 9, 2019
Closed
@mikaelm12 mikaelm12 added the Done This issue has been fixed label Apr 9, 2019
@analogrelay analogrelay added the accepted This issue has completed "acceptance" testing (including accessibility) label Apr 16, 2019
@ghost ghost locked as resolved and limited conversation to collaborators Dec 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@mikaelm12 mikaelm12

Labels
accepted This issue has completed "acceptance" testing (including accessibility) area-signalr Includes: SignalR clients and servers Done This issue has been fixed feature-client-java Related to the SignalR Java client feature-client-javascript Related to the SignalR JS client feature-client-net Related to the SignalR .NET client
Projects
None yet
Milestone
3.0.0-preview4
Development

No branches or pull requests
3 participants
@analogrelay @halter73 @mikaelm12