On Tuesday, 16 August 2016 at 09:16:40 UTC, yawniek wrote:
> imo things should be modularized.
>
> so there should be (fast) protocol parsers first, something like
>
> https://github.com/h2o/picohttpparser or
> https://github.com/seanmonstar/httparse
>
> then a very simple eventloop that has abstractions and range based interfaces for reading/writing data into different types of sockets.

There is common http message parser that used in nginx and nodejs. I think it can be ported from C to D. Both sync and async code can be built around this parser. But async library accepted as standard need before this.

On Tuesday, 16 August 2016 at 10:06:05 UTC, ikod wrote:
> On Tuesday, 16 August 2016 at 09:16:40 UTC, yawniek wrote:
>
> There is common http message parser that used in nginx and nodejs. I think it can be ported from C to D.

that is pico, see:
https://github.com/nodejs/http-parser/pull/200
https://github.com/h2o/picohttpparser/issues/7

>  But async library accepted as standard need before this.
i don't think there is any temporal dependency between an eventloop and a http parser making it into phobos.
only later then a simple http server or client needs both (+ TLS ).