Rémy F.

I think this issue can now be closed. Until we found another hole in the API to avoid using ARL

Okay here is an update. - socket are now part of `os` - `socket()` now use 2 args (family, type) - `backlog=10` is kept as optional arg for listen -...

> if you want to keep the socket api low-level For now yes, because all `os` IO function are made that way (synchronous). Note that existing `os.setReadHandler()`, `os.setWriteHandler()` offer an...

> If you can also use os.setReadHandler() after listen() and os.setWriteHandler() after a connect() call, then I think everything is covered. Have you tested that? I tested it (both on...

- I meant `it also call the handler when there is nothing to recv.` => indeed because the fd was closed. So a correct handler would need to unregister itself:...

* poll() API removed * reverted js_os_poll to be the event loop pooling * more JS_*() catched (sorry I'll do a global pass at the end) * IPv6 shall now...

I've finished the api and it's a joy to play with so @ceedriic don't hésitante to play with CHANGES: - changed `sendto` arguments order to keep the `length?` last and...

@bellard : JS sockets are working with winsock2 API (tested HTTP client + HTTP server via wine/mingw32_64) I'm unsure about the os_poll part, so your mentoring would be appreciated. In...

@bellard done :heavy_check_mark: Also, returned `addrinfo[]` objects now also have an additional `socktype` property to be used to create sockets. ```js const [addr] = must(os.getaddrinfo("bellard.org", { service: 80 })); const...