[swift-server-dev] HTTP Parser

Helge Heß me at helgehess.eu
Thu Nov 3 15:34:24 CDT 2016

On 3 Nov 2016, at 19:41, Alfredo Delli Bovi <alfredo.dellibovi at gmail.com> wrote:
> There has been some discussions about this in Kitura already (https://github.com/IBM-Swift/Kitura-net/issues/52) and I think we can use what they found out at the moment.
> In my opinion, if we are not able to give the same (or better) performance we should go for a wrapper of a more performant lib, such as http_parser.

They claim that their port is just ~1/3 slower, that seems perfectly reasonable to me. I’m all for using it.

I also agree with the overall sentiment that a ‘pure’ Swift solution should be preferred.

> Of course it’s also matter of the workload that have, we could always start with a wrapper, so we are able to define the APIs layer and ship a version with it and later on changing the implementation with a pure Swift.

Yes, the API should sit on top of this and be essentially parser agnostic.


More information about the swift-server-dev mailing list