[swift-server-dev] HTTP Parser

[Tanner Nelson]

Tanner Nelson
Vapor 
+1 (435) 773-2831

> On Nov 3, 2016, at 4:34 PM, Helge Heß via swift-server-dev <swift-server-dev at swift.org> wrote:
> 
> 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.

As far as I can tell, the package in question here is a carbon copy of the C parser (UnsafePointers, asserts, global funcs). The only difference is it's 1/3 slower. 

A big performance hit like that is not worth it unless we're getting improved readability or safety out of the code. 

> 
> 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.
> 
> hh
> 
> _______________________________________________
> swift-server-dev mailing list
> swift-server-dev at swift.org
> https://lists.swift.org/mailman/listinfo/swift-server-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-server-dev/attachments/20161103/b43b6b36/attachment.html>