<font size=2 face="sans-serif">Both Perfect and Node.js use the same C
HTTP parser that's being referred to.</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">Wayne N 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</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">17/11/2016 16:56</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><font size=3>Tyler Cloutier,</font>
<br>
<br><font size=3>Proposing Node.js HTTP in C would need some benchmark
for a comparison which I assume it would be slower than native Node.js
and Perfect using HTTP in C.</font>
<br>
<br><a href="https://medium.com/@rymcol/linux-ubuntu-benchmarks-for-server-side-swift-vs-node-js-db52b9f8270b#.hori7khr1"><font size=3 color=blue><u>https://medium.com/@rymcol/linux-ubuntu-benchmarks-for-server-side-swift-vs-node-js-db52b9f8270b#.hori7khr1</u></font></a>
<br>
<br><font size=3>On Wed, Nov 16, 2016 at 12:54 AM, Logan Wright via swift-server-dev <</font><a href="mailto:swift-server-dev@swift.org" target=_blank><font size=3 color=blue><u>swift-server-dev@swift.org</u></font></a><font size=3>> wrote:</font>
<br><font size=3>Chris,</font>
<br>
<br><font size=3>That sounds perfect, webex has been a great format so
far. Right now it's looking like 12 eastern time on the 21st or the 23rd.</font>
<br>
<br><font size=3>- Logan</font>
<br>
<br><font size=3>On Tue, Nov 15, 2016 at 9:32 AM Chris Bailey <</font><a href=mailto:BAILEYC@uk.ibm.com target=_blank><font size=3 color=blue><u>BAILEYC@uk.ibm.com</u></font></a><font size=3>>
wrote:</font>
<br><font size=2 face="sans-serif">Thanks for setting this up. I've filled
out the Doodle Poll - do you need/want me to set up a Webex once we've
determined the day/time?</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Chris</font><font size=3><br>
<br>
<br>
<br>
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
From: </font><font size=1 face="sans-serif">Logan
Wright via swift-server-dev <</font><a href="mailto:swift-server-dev@swift.org" target=_blank><font size=1 color=blue face="sans-serif"><u>swift-server-dev@swift.org</u></font></a><font size=1 face="sans-serif">></font><font size=3> </font><font size=1 color=#5f5f5f face="sans-serif"><br>
To: </font><font size=1 face="sans-serif">Paulo
Faria <</font><a href=mailto:paulo@zewo.io target=_blank><font size=1 color=blue face="sans-serif"><u>paulo@zewo.io</u></font></a><font size=1 face="sans-serif">></font><font size=3> </font><font size=1 color=#5f5f5f face="sans-serif"><br>
Cc: </font><a href="mailto:swift-server-dev@swift.org" target=_blank><font size=1 color=blue face="sans-serif"><u>swift-server-dev@swift.org</u></font></a><font size=3> </font><font size=1 color=#5f5f5f face="sans-serif"><br>
Date: </font><font size=1 face="sans-serif">11/11/2016
03:07</font><font size=3> </font><font size=1 color=#5f5f5f face="sans-serif"><br>
Subject: </font><font size=1 face="sans-serif">Re:
[swift-server-dev] HTTP Parser</font><font size=3> </font><font size=1 color=#5f5f5f face="sans-serif"><br>
Sent by: </font><a href="mailto:swift-server-dev-bounces@swift.org" target=_blank><font size=1 color=blue face="sans-serif"><u>swift-server-dev-bounces@swift.org</u></font></a><font size=3> <br>
</font>
<hr noshade><font size=3><br>
<br>
<br>
Good catch Paulo, fixed, make sure to double check your selections in case
it moved any of them on you. <br>
<br>
On Thu, Nov 10, 2016 at 10:03 PM Paulo Faria <</font><a href=mailto:paulo@zewo.io target=_blank><font size=3 color=blue><u>paulo@zewo.io</u></font></a><font size=3>>
wrote: <br>
I think on Tue 22 the first choice shouldn’t be there? For my timezone
it says 2AM and right next to it there’s a 2PM. <br>
<br>
<br>
On Nov 11, 2016, at 12:57 AM, Logan Wright via swift-server-dev <</font><a href="mailto:swift-server-dev@swift.org" target=_blank><font size=3 color=blue><u>swift-server-dev@swift.org</u></font></a><font size=3>>
wrote: <br>
<br>
Hey everyone, I think it's about time we do some of the http sub-team kickoff.
We can discuss some of the topics in here and more generally start breaking
off.<br>
<br>
Here's the doodle for interested. We're shooting for the week of the 21st.
We'll also collect minutes for those who can't make it. </font><font size=3 color=blue><u><br>
<br>
</u></font><a href=http://doodle.com/poll/e2tffhkaergtd72p target=_blank><font size=3 color=blue><u>http://doodle.com/poll/e2tffhkaergtd72p</u></font></a><font size=3><br>
<br>
- Logan <br>
<br>
On Thu, Nov 10, 2016 at 2:48 AM Tyler Cloutier via swift-server-dev <</font><a href="mailto:swift-server-dev@swift.org" target=_blank><font size=3 color=blue><u>swift-server-dev@swift.org</u></font></a><font size=3>>
wrote: <br>
Additionally, we are proposing using the Node.js, C language, HTTP parser
which has been tested in thousands upon thousands of currently deployed
applications so the likelihood of errors would be much lower than for a
home grown solution.<br>
<br>
That being said I do appreciate the desire to be inclusive of developers
who might not be familiar with C. Not to mention the benefits of safety
provided by Swift. I just think in this case since the proposed parser
is so well tested and widely use, it would be the safer option to choose
that.<br>
<br>
Tyler<br>
<br>
<br>
> On Nov 8, 2016, at 11:26 PM, Jean-Daniel via swift-server-dev <</font><a href="mailto:swift-server-dev@swift.org" target=_blank><font size=3 color=blue><u>swift-server-dev@swift.org</u></font></a><font size=3>>
wrote:<br>
><br>
><br>
>> Le 7 nov. 2016 à 16:46, James Lei via swift-server-dev <</font><a href="mailto:swift-server-dev@swift.org" target=_blank><font size=3 color=blue><u>swift-server-dev@swift.org</u></font></a><font size=3>>
a écrit :<br>
>><br>
>> if HTTP Parser in C is use along with Swift, it may be difficult
for the Startups and Enterprise to adopt as an early adopters if something
will break, it would be difficult for the developers to debug if it's cause
by C or Swift.<br>
>><br>
>> I favour writing in Swift from scratch to encourage software engineers
and the like to participate on the same languages from .Net, Java, Node.js,
Go, Rust community, etc<br>
>><br>
>> Who will be our early adopters?<br>
><br>
> If the primary users are the frameworks authors, I’m pretty sure
the final users won't care if the low level stuff are C wrappers or a pure
swift as long as it work out of the box and they can deploy and use the
framework easily.<br>
><br>
><br>
><br>
> _______________________________________________<br>
> swift-server-dev mailing list<br>
> </font><a href="mailto:swift-server-dev@swift.org" target=_blank><font size=3 color=blue><u>swift-server-dev@swift.org</u></font></a><font size=3><br>
> </font><a href="https://lists.swift.org/mailman/listinfo/swift-server-dev" target=_blank><font size=3 color=blue><u>https://lists.swift.org/mailman/listinfo/swift-server-dev</u></font></a><font size=3><br>
<br>
_______________________________________________<br>
swift-server-dev mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:swift-server-dev@swift.org" target=_blank><font size=3 color=blue><u>swift-server-dev@swift.org</u></font></a><font size=3 color=blue><u><br>
</u></font><a href="https://lists.swift.org/mailman/listinfo/swift-server-dev" target=_blank><font size=3 color=blue><u>https://lists.swift.org/mailman/listinfo/swift-server-dev</u></font></a><font size=3> <br>
_______________________________________________<br>
swift-server-dev mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:swift-server-dev@swift.org" target=_blank><font size=3 color=blue><u>swift-server-dev@swift.org</u></font></a><font size=3 color=blue><u><br>
</u></font><a href="https://lists.swift.org/mailman/listinfo/swift-server-dev" target=_blank><font size=3 color=blue><u>https://lists.swift.org/mailman/listinfo/swift-server-dev</u></font></a><font size=3> </font><tt><font size=2><br>
_______________________________________________<br>
swift-server-dev mailing list</font></tt><tt><font size=2 color=blue><u><br>
</u></font></tt><a href="mailto:swift-server-dev@swift.org" target=_blank><tt><font size=2 color=blue><u>swift-server-dev@swift.org</u></font></tt></a><font size=3 color=blue><u><br>
</u></font><a href="https://lists.swift.org/mailman/listinfo/swift-server-dev" target=_blank><tt><font size=2 color=blue><u>https://lists.swift.org/mailman/listinfo/swift-server-dev</u></font></tt></a><font size=3><br>
<br>
</font><font size=2 face="sans-serif"><br>
<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</font>
<br><font size=3><br>
_______________________________________________<br>
swift-server-dev mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:swift-server-dev@swift.org"><font size=3 color=blue><u>swift-server-dev@swift.org</u></font></a><font size=3 color=blue><u><br>
</u></font><a href="https://lists.swift.org/mailman/listinfo/swift-server-dev" target=_blank><font size=3 color=blue><u>https://lists.swift.org/mailman/listinfo/swift-server-dev</u></font></a><tt><font size=2>_______________________________________________<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>