@yagiznizipli ok i am a bit wrong about the event loop part. spiderfire (the underlying library that winterjs is using) does handle event loop integration.
@yagiznizipli the source code is such a sad story... it recreates the entire spidermoney runtime from scratch for every http request, including reparsing&reevaluating the user code. there is no integration between js event loop and tokio so the entire request handler is effectively blocking
@NicoloRibaudo can we please stop giving obvious grift from wasmer attention? this isn't even the first time they've tried to namejack an open spec. this isn't even the second time they've tried to namejack an open spec.
my change to allow http(s) schemes and relative urls in `new WebSocket()` seems to have finally been merged into the spec :) thanks for pushing it through @annevk
@jonsneyers Thanks for the example this is super helpful. In case you're stressed, I can confirm the original file is not damaged, this is just some of our intermediate servers re-encoding it.