Erik Dubbelboer

Looks like he never pushed these modifications to his fork: https://github.com/refaktor/MooComplete/branches I haven't look at this code in years but I guess you could add an `onSelect` to the options...

I'll add something for vhosts soon. With HTTP long connection you mean keep alive connections?

To be honest I have no experience with Mac virtual machines so I don't know. I do know that travis runs multiple tests on the same machines so they might...

I have just made a pull request where I switch all timing code to use `process.hrtime()`: https://github.com/erikdubbelboer/node-sleep/pull/103 Here everything seems to be working fine: https://travis-ci.org/erikdubbelboer/node-sleep/builds/630569802?utm_source=github_status&utm_medium=notification My guess is 100 milliseconds...

It doesn't generate garbage. That's exactly why we have these tests: https://github.com/valyala/fasthttp/blob/master/allocation_test.go What it does do is allocate memory that will be reused over time. And of course it will...

What is generating the `no free connections available to host` message? Have you tried measuring how many concurrent requests you are receiving and if `10000` connections is enough for that?...

How many requests are you sending per second before you get that error? How long does your handler take to send a response?

Something like that could work but it would still have to return an error. It will leave the connection in a broken state with a partially read body. It will...

I would be open to a pull request to add a method to expose this. But it needs some good documentation to make clear what it's for.

The handler sets the status code which is captured by `netHTTPResponseWriter` and then line 65 propagates that to the Response. Can you show an example of something going wrong?