4 ms·
Browsers limit the ability for these platforms to use raw sockets, there simply is no API for it. The best that can be done /today/ is to use WebSockets, which
by SethMLarson 3y ago
Browsers limit the ability for these platforms to use raw sockets, there simply is no API for it. The best that can be done /today/ is to use WebSockets, which are not the same thing and can't be used for HTTP requests without the server expecting a WebSocket connection:
https://github.com/emscripten-core/emscripten/issues/5196#issuecomment-299442038 https://github.com/emscripten-core/emscripten/issues/5196#is...
- SushiHippie 3y agoSure, sorry if it wasn't clear from my question, it wasn't specifically about urllib3, but I meant if there are plans that browsers will make such an API available or if this is something that will never become real.
- sillysaurusx 3y agoI doubt browsers would allow this, though gamedevs have wanted it for decades now. Particularly UDP.
- plopz 3y agoisn't the udp problem fixed with http3 unreliable webtransport?
- sillysaurusx 3y agoIs it? That would be cool. Under the hood is it actual udp?
- SushiHippie 3y agoHTTP3 uses QUIC, it's not "pure" UDP, but it's a protocol based on it https://en.wikipedia.org/wiki/QUIC https://en.wikipedia.org/wiki/QUIC
- plopz 3y agoits udp with encryption and congestion control, but the aspects that gamedevs like about udp, low latency and out of order delivery without head of line blocking are features https://developer.chrome.com/docs/capabilities/web-apis/webtransport https://developer.chrome.com/docs/capabilities/web-apis/webt...