Uh oh!
There was an error while loading. Please reload this page.
[browser] WS & HTTP clients more async - #95483
Conversation
ghost
commented
Nov 30, 2023
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsMotivationI would like to make dispatch of async Changes
|
pavelsavara
commented
Nov 30, 2023
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
pavelsavara
commented
Dec 1, 2023
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
# Conflicts: # src/mono/wasm/runtime/cancelable-promise.ts
pavelsavara
commented
Dec 2, 2023
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
pavelsavara
commented
Dec 2, 2023
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