Skip to content
Discussion options

You must be logged in to vote

For WASM, it's generally either one of two reasons:

  1. The feature as-is cannot exist on WASM. For example, since WASM in the browser is just using fetch, we cannot enable or disable TLS, or really configure it.
  2. No has gotten around to implementing it. In particular, I don't have concrete usage of WASM that pushes the development, so it's all based on other contributors when they need it. It was only recently that timeout support was added, making use of setTimeout and AbortController internally.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@antoniosarosi
Comment options

Answer selected by Khotam
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants
Converted from issue

This discussion was converted from issue #2561 on February 21, 2025 19:58.