Skip to content

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

Open
analogrelay opened this issue Mar 21, 2019 · 5 comments
Open

Review Options for signalr C++ client #8716

analogrelay opened this issue Mar 21, 2019 · 5 comments
Labels
affected-few This issue impacts only small number of customers area-signalr Includes: SignalR clients and servers feature-client-c++ Related to the SignalR C++ client severity-minor This label is used by an internal tool task
Milestone

Comments

@analogrelay
Copy link
Contributor

analogrelay commented Mar 21, 2019

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.)

@analogrelay analogrelay added cost: S area-signalr Includes: SignalR clients and servers feature-client-c++ Related to the SignalR C++ client labels Mar 21, 2019
@analogrelay analogrelay added this to the 3.0.0-preview5 milestone Mar 21, 2019
@analogrelay analogrelay modified the milestones: 3.0.0-preview7, Backlog May 30, 2019
@analogrelay analogrelay modified the milestones: Backlog, 5.0.0 Jul 30, 2019
@analogrelay
Copy link
Contributor Author

Another one to make sure we cover is "skip negotiation" (#21386)

@wegylexy
Copy link
Contributor

See aspnet/SignalR-Client-Cpp#33

@BrennanConroy BrennanConroy modified the milestones: 5.0.0, Backlog Jul 27, 2020
@ghost
Copy link

ghost commented Jul 27, 2020

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.

@pranavkm pranavkm removed the cost: S label Nov 6, 2020
@BrennanConroy BrennanConroy added affected-few This issue impacts only small number of customers severity-minor This label is used by an internal tool task labels Nov 11, 2020 — with ASP.NET Core Issue Ranking
@BrennanConroy
Copy link
Member

  • Connection timeout, 5 seconds by default, times out http requests/negotiate
  • Consider adding scheduler settings, right now we spin up 5 threads

@davidfowl
Copy link
Member

@BrennanConroy are these issues still relevant or are we tracking the client work separately?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affected-few This issue impacts only small number of customers area-signalr Includes: SignalR clients and servers feature-client-c++ Related to the SignalR C++ client severity-minor This label is used by an internal tool task
Projects
None yet
Development

No branches or pull requests

5 participants