<div dir="ltr">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. <br><br><a href="http://doodle.com/poll/e2tffhkaergtd72p">http://doodle.com/poll/e2tffhkaergtd72p</a><br><br>- Logan</div><br><div class="gmail_quote"><div dir="ltr">On Thu, Nov 10, 2016 at 2:48 AM Tyler Cloutier via swift-server-dev <<a href="mailto:swift-server-dev@swift.org">swift-server-dev@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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 class="gmail_msg">
<br class="gmail_msg">
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 class="gmail_msg">
<br class="gmail_msg">
Tyler<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
> On Nov 8, 2016, at 11:26 PM, Jean-Daniel via swift-server-dev <<a href="mailto:swift-server-dev@swift.org" class="gmail_msg" target="_blank">swift-server-dev@swift.org</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
>> Le 7 nov. 2016 à 16:46, James Lei via swift-server-dev <<a href="mailto:swift-server-dev@swift.org" class="gmail_msg" target="_blank">swift-server-dev@swift.org</a>> a écrit :<br class="gmail_msg">
>><br class="gmail_msg">
>> 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 class="gmail_msg">
>><br class="gmail_msg">
>> 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 class="gmail_msg">
>><br class="gmail_msg">
>> Who will be our early adopters?<br class="gmail_msg">
><br class="gmail_msg">
> 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 class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
> _______________________________________________<br class="gmail_msg">
> swift-server-dev mailing list<br class="gmail_msg">
> <a href="mailto:swift-server-dev@swift.org" class="gmail_msg" target="_blank">swift-server-dev@swift.org</a><br class="gmail_msg">
> <a href="https://lists.swift.org/mailman/listinfo/swift-server-dev" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-server-dev</a><br class="gmail_msg">
<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
swift-server-dev mailing list<br class="gmail_msg">
<a href="mailto:swift-server-dev@swift.org" class="gmail_msg" target="_blank">swift-server-dev@swift.org</a><br class="gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-server-dev" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-server-dev</a><br class="gmail_msg">
</blockquote></div>