-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[browser] WS & HTTP clients more async #95483
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
Conversation
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsMotivationI would like to make dispatch of async Changes
|
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
...System.Net.WebSockets.Client/src/System/Net/WebSockets/BrowserWebSockets/BrowserWebSocket.cs
Outdated
Show resolved
Hide resolved
...JavaScript/src/System/Runtime/InteropServices/JavaScript/SynchronizationContextExtensions.cs
Outdated
Show resolved
Hide resolved
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
# Conflicts: # src/mono/wasm/runtime/cancelable-promise.ts
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Unrelated MT failure: Log |
Motivation
I would like to make dispatch of async
JSImportonto different thread automatic inside of theJSImportinternals.Draft here
It will have similar effect for the WS+HTTP clients like this change.
So I'm making the necessary changes ahead of time here.
Changes
nullas synchronous singnal in the MT implementation of WSSynchronizationContext.PostinsteadSendwhere the underlying method is async