<font size=2 face="sans-serif">>> </font><tt><font size=2>But it
sounds like MIT licensed code can’t be used as part of the effort, maybe
that should be added the the front-page of the effort.</font></tt>
<br>
<br><font size=2 face="sans-serif">I'm not 100% convinced this is true.
There's nothing (legally) preventing the inclusion of MIT licensed code
in a Apache 2.0 licensed product, you just may have to list some Product
Unique Terms (PUTs) to cover it - we don't need the Node.js community to
dual-license it for us to use it. Parts of the Swift toolchain already
have compiled-in dependencies on MIT licensed code, so my guess is that
ship has already sailed on using non-Apache 2.0 licensed code.</font>
<br>
<br><font size=2 face="sans-serif">Having said that, we'd obviously need
a read and approval from the Swift Core Team (and Apple legal!) before
making a compiled-in dependency on anything.</font>
<br>
<br><font size=2 face="sans-serif">Chris</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Helge Heß via swift-server-dev
<swift-server-dev@swift.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"swift-server-dev@swift.org"
<swift-server-dev@swift.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">20/11/2016 18:08</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [swift-server-dev]
HTTP Parser</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">swift-server-dev-bounces@swift.org</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>Hi Dave,<br>
<br>
thanks for your post, this detail is indeed quite helpful.<br>
<br>
I don’t think anyone seriously suggested using a Swift port of the http_parser
but instead just the upstream C one. But it sounds like MIT licensed code
can’t be used as part of the effort, maybe that should be added the the
front-page of the effort.<br>
<br>
I assume it is not a huge issue though as a libhttp_parser can be shipped
separately from Swift itself, similar to what you would do for OpenSSL
etc (and what is already being done with libcurl on Linux).<br>
<br>
In any case: Whatever is decided, it at least establishes a performance
characteristic, I think any replacement should accomplish a comparable
one - preferably faster of course :-)<br>
<br>
hh<br>
<br>
<br>
> On 20 Nov 2016, at 16:58, David Sperling via swift-server-dev <swift-server-dev@swift.org>
wrote:<br>
> <br>
> I would like to provide some additional detail to the discussion on
November 4 (which I missed since I joined recently).<br>
> <br>
> The team pointed out this thread in Kitura which I initially opened:<br>
> </font></tt><a href="https://github.com/IBM-Swift/Kitura-net/issues/52"><tt><font size=2>https://github.com/IBM-Swift/Kitura-net/issues/52</font></tt></a><tt><font size=2><br>
> <br>
> Here is the referenced Swift http_parser project which I initially
ported as a thought experiment. The goals, API and performance are
described in the readme.<br>
> </font></tt><a href=https://github.com/smithmicro/HTTPParser><tt><font size=2>https://github.com/smithmicro/HTTPParser</font></tt></a><tt><font size=2><br>
> <br>
> Michael Gottesman from Apple (@gottesmm) contacted me 2 weeks ago
to see if we could add the project into the Swift Benchmark Suite. See
the bottom of this PR for the request:<br>
> </font></tt><a href="https://github.com/IBM-Swift/Kitura-net/pull/55"><tt><font size=2>https://github.com/IBM-Swift/Kitura-net/pull/55</font></tt></a><tt><font size=2><br>
> <br>
> Michael and I approached the Node.js Foundation to see if they were
willing to dual license http_parser under Apache 2 so it would be compatible
with the Swift license. Here is that discussion, but in summary,
a dual license is not realistic.<br>
> </font></tt><a href="https://github.com/nodejs/http-parser/issues/344"><tt><font size=2>https://github.com/nodejs/http-parser/issues/344</font></tt></a><tt><font size=2><br>
> <br>
> So, a http_parser Swift port:<br>
> - Would not have the proper license to be included in Swift<br>
> - Does not take full advantage of Swift<br>
> - Has the issues previously pointed out (UnsafePointers, asserts,
throws simulating gotos)<br>
> - Does, however, demonstrate a Swift HTTP parser performance of 500K
requests per second<br>
> <br>
> <br>
> Looking forward to meeting everyone on our call tomorrow. Hopefully
this detail was helpful.<br>
> <br>
> <br>
> Dave Sperling<br>
> Smith Micro<br>
<br>
_______________________________________________<br>
swift-server-dev mailing list<br>
swift-server-dev@swift.org<br>
</font></tt><a href="https://lists.swift.org/mailman/listinfo/swift-server-dev"><tt><font size=2>https://lists.swift.org/mailman/listinfo/swift-server-dev</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br><font size=2 face="sans-serif"><br>
Unless stated otherwise above:<br>
IBM United Kingdom Limited - Registered in England and Wales with number
741598. <br>
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU<br>
</font>