-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Review Options for signalr C++ client #8716
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.
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
Comments
Another one to make sure we cover is "skip negotiation" (#21386) |
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
|
@BrennanConroy are these issues still relevant or are we tracking the client work separately? |
Epic #5301
We need to review the options model for the SignalR C++ client. Especially around authentication (making sure we support a custom auth token) and providing implementations of our abstractions (http_client, websocket_client, etc.)
The text was updated successfully, but these errors were encountered: