<div dir="ltr">Chris,<div><br></div><div>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.</div><div><br></div><div>- Logan</div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Nov 15, 2016 at 9:32 AM Chris Bailey <<a href="mailto:BAILEYC@uk.ibm.com">BAILEYC@uk.ibm.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font size="2" face="sans-serif" class="gmail_msg">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>
<br class="gmail_msg">
<br class="gmail_msg"><font size="2" face="sans-serif" class="gmail_msg">Chris<br class="gmail_msg">
</font>
<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg"><font size="1" color="#5f5f5f" face="sans-serif" class="gmail_msg">From:
</font><font size="1" face="sans-serif" class="gmail_msg">Logan Wright via swift-server-dev
<<a href="mailto:swift-server-dev@swift.org" class="gmail_msg" target="_blank">swift-server-dev@swift.org</a>></font>
<br class="gmail_msg"><font size="1" color="#5f5f5f" face="sans-serif" class="gmail_msg">To:
</font><font size="1" face="sans-serif" class="gmail_msg">Paulo Faria <<a href="mailto:paulo@zewo.io" class="gmail_msg" target="_blank">paulo@zewo.io</a>></font>
<br class="gmail_msg"><font size="1" color="#5f5f5f" face="sans-serif" class="gmail_msg">Cc:
</font><font size="1" face="sans-serif" class="gmail_msg"><a href="mailto:swift-server-dev@swift.org" class="gmail_msg" target="_blank">swift-server-dev@swift.org</a></font>
<br class="gmail_msg"><font size="1" color="#5f5f5f" face="sans-serif" class="gmail_msg">Date:
</font><font size="1" face="sans-serif" class="gmail_msg">11/11/2016 03:07</font>
<br class="gmail_msg"><font size="1" color="#5f5f5f" face="sans-serif" class="gmail_msg">Subject:
</font><font size="1" face="sans-serif" class="gmail_msg">Re: [swift-server-dev]
HTTP Parser</font>
<br class="gmail_msg"><font size="1" color="#5f5f5f" face="sans-serif" class="gmail_msg">Sent by:
</font><font size="1" face="sans-serif" class="gmail_msg"><a href="mailto:swift-server-dev-bounces@swift.org" class="gmail_msg" target="_blank">swift-server-dev-bounces@swift.org</a></font>
<br class="gmail_msg">
<hr noshade class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg"><font size="3" class="gmail_msg">Good catch Paulo, fixed, make sure to double check your
selections in case it moved any of them on you.</font>
<br class="gmail_msg">
<br class="gmail_msg"><font size="3" class="gmail_msg">On Thu, Nov 10, 2016 at 10:03 PM Paulo Faria <</font><a href="mailto:paulo@zewo.io" class="gmail_msg" target="_blank"><font size="3" color="blue" class="gmail_msg"><u class="gmail_msg">paulo@zewo.io</u></font></a><font size="3" class="gmail_msg">>
wrote:</font>
<br class="gmail_msg"><font size="3" class="gmail_msg">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. </font>
<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg"><font size="3" class="gmail_msg">On Nov 11, 2016, at 12:57 AM, Logan Wright via swift-server-dev
<</font><a href="mailto:swift-server-dev@swift.org" class="gmail_msg" target="_blank"><font size="3" color="blue" class="gmail_msg"><u class="gmail_msg">swift-server-dev@swift.org</u></font></a><font size="3" class="gmail_msg">>
wrote:</font>
<br class="gmail_msg">
<br class="gmail_msg"><font size="3" class="gmail_msg">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 class="gmail_msg">
<br class="gmail_msg">
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 class="gmail_msg">
</font><font size="3" color="blue" class="gmail_msg"><u class="gmail_msg"><br class="gmail_msg">
</u></font><a href="http://doodle.com/poll/e2tffhkaergtd72p" class="gmail_msg" target="_blank"><font size="3" color="blue" class="gmail_msg"><u class="gmail_msg">http://doodle.com/poll/e2tffhkaergtd72p</u></font></a><font size="3" class="gmail_msg"><br class="gmail_msg">
<br class="gmail_msg">
- Logan</font>
<br class="gmail_msg">
<br class="gmail_msg"><font size="3" class="gmail_msg">On Thu, Nov 10, 2016 at 2:48 AM Tyler Cloutier via swift-server-dev
<</font><a href="mailto:swift-server-dev@swift.org" class="gmail_msg" target="_blank"><font size="3" color="blue" class="gmail_msg"><u class="gmail_msg">swift-server-dev@swift.org</u></font></a><font size="3" class="gmail_msg">>
wrote:</font>
<br class="gmail_msg"><font size="3" class="gmail_msg">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 <</font><a href="mailto:swift-server-dev@swift.org" class="gmail_msg" target="_blank"><font size="3" color="blue" class="gmail_msg"><u class="gmail_msg">swift-server-dev@swift.org</u></font></a><font size="3" class="gmail_msg">>
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 <</font><a href="mailto:swift-server-dev@swift.org" class="gmail_msg" target="_blank"><font size="3" color="blue" class="gmail_msg"><u class="gmail_msg">swift-server-dev@swift.org</u></font></a><font size="3" class="gmail_msg">>
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">
> </font><a href="mailto:swift-server-dev@swift.org" class="gmail_msg" target="_blank"><font size="3" color="blue" class="gmail_msg"><u class="gmail_msg">swift-server-dev@swift.org</u></font></a><font size="3" class="gmail_msg"><br class="gmail_msg">
> </font><a href="https://lists.swift.org/mailman/listinfo/swift-server-dev" class="gmail_msg" target="_blank"><font size="3" color="blue" class="gmail_msg"><u class="gmail_msg">https://lists.swift.org/mailman/listinfo/swift-server-dev</u></font></a><font size="3" class="gmail_msg"><br class="gmail_msg">
<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
swift-server-dev mailing list</font><font size="3" color="blue" class="gmail_msg"><u class="gmail_msg"><br class="gmail_msg">
</u></font><a href="mailto:swift-server-dev@swift.org" class="gmail_msg" target="_blank"><font size="3" color="blue" class="gmail_msg"><u class="gmail_msg">swift-server-dev@swift.org</u></font></a><font size="3" color="blue" class="gmail_msg"><u class="gmail_msg"><br class="gmail_msg">
</u></font><a href="https://lists.swift.org/mailman/listinfo/swift-server-dev" class="gmail_msg" target="_blank"><font size="3" color="blue" class="gmail_msg"><u class="gmail_msg">https://lists.swift.org/mailman/listinfo/swift-server-dev</u></font></a>
<br class="gmail_msg"><font size="3" class="gmail_msg">_______________________________________________<br class="gmail_msg">
swift-server-dev mailing list</font><font size="3" color="blue" class="gmail_msg"><u class="gmail_msg"><br class="gmail_msg">
</u></font><a href="mailto:swift-server-dev@swift.org" class="gmail_msg" target="_blank"><font size="3" color="blue" class="gmail_msg"><u class="gmail_msg">swift-server-dev@swift.org</u></font></a><font size="3" color="blue" class="gmail_msg"><u class="gmail_msg"><br class="gmail_msg">
</u></font><a href="https://lists.swift.org/mailman/listinfo/swift-server-dev" class="gmail_msg" target="_blank"><font size="3" color="blue" class="gmail_msg"><u class="gmail_msg">https://lists.swift.org/mailman/listinfo/swift-server-dev</u></font></a>
<br class="gmail_msg"><tt class="gmail_msg"><font size="2" 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">
</font></tt><a href="https://lists.swift.org/mailman/listinfo/swift-server-dev" class="gmail_msg" target="_blank"><tt class="gmail_msg"><font size="2" class="gmail_msg">https://lists.swift.org/mailman/listinfo/swift-server-dev</font></tt></a><tt class="gmail_msg"><font size="2" class="gmail_msg"><br class="gmail_msg">
</font></tt>
<br class="gmail_msg">
<br class="gmail_msg"><font size="2" face="sans-serif" class="gmail_msg"><br class="gmail_msg">
Unless stated otherwise above:<br class="gmail_msg">
IBM United Kingdom Limited - Registered in England and Wales with number
741598. <br class="gmail_msg">
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU<br class="gmail_msg">
</font>
</blockquote></div>