Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
v5 Request - Adopt Async/Task based requests
See original GitHub issueIssue Type
- Feature Request
Describe the issue
Currently all calls to do requests with OBS are synchronous not making use of Task (and potentially async), given there has been a large push to move towards this paradigm by a lot of vendors who can do potentially long running tasks, i.e IO, Network, API, DB calls etc it would be good if we could provide async compatible requests.
Versions OBS Version: N/A OBS WebSocket Version: 5.x OBS WebSocket Dotnet (this library) Version: 5.x OS: N/A
Additional context There was a PR offered for the v4 branch which included these changes which allowed for mainly non blocking requests to OBS which helps greatly with UI facing applications, unfortunately that PR never made it through, but it would be great if the same approaches could be rolled into the v5 branch.
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
How about this?
However you spin it, bare minimum its going to need to change the signatures of almost all request methods from
T Whatever()toTask<T> Whatever()and all the corresponding methods related to it as well as cancellation token parts as well.So just to make sure we are on the same page this will ultimately have cascading changes everywhere, but the PR (assuming im the one who does it) will JUST be related to this issue.