> Is it actually supposed to be a server rather than a client? It's supposed to be both: receive a request, send a request to another host, and receive the response.
> You can of course not use async, In fact, that would be the thing I need. I don't mind blocking while waiting for responses. But I couldn't find an blocking HTTP server in the stdlib, and implementing it myself with sockets sounds like an overkill. > why is it so bad to simply use await or waitFor at the call site? Could you please elaborate a bit on that? I don't mind doing something like `waitFor acceptRequest`. Is there a ready-to-use proc for that, or do you mean I should implement it by reading from socket?
