<div dir="ltr"><div dir="ltr" class="gmail_msg"><div dir="ltr" class="gmail_msg">Helge,<br class="gmail_msg"><br class="gmail_msg">At some point someone has to do the work, yes, but ultimately there are a lot of stakeholders to consider and if there's a chance that they can all find common ground, then it must be pursued. The point of this group is to provide base level APIs that can work with the existing frameworks in a way that adds value. Apple isn't going to do this (or has at least made no indication of any interest whatsoever), and for IBM to just do it, I don't think choosing one framework to steamroll is the answer and defeats the purpose of the group. Technically there are many reference implementations already, Kitura, Perfect, Vapor, Foundation to some degree.<br class="gmail_msg"><br class="gmail_msg">Things like sockets/security/crypto are easily agreed upon and moved forward with little impact to existing frameworks. The HTTP models and architecture have by far the greatest impact of any other feature of the server side group and so the discussion will take as long as it needs to in order to get it right. The existing frameworks have a lot of experience in these areas for what has worked and what hasn't, and they all have existing architectures and paradigms that need to be accounted for as much as possible.<br class="gmail_msg"><br class="gmail_msg">There has already been a great deal of compromise on the parsing and serialization layer, and I'm confident we can get somewhere with models as well. I'd personally like to see us more explicitly explore protocols, I haven't seen anything so far that actually requires a concrete model and would perhaps be an easier way for us to reach consensus. In the meantime, I think it's important to get something that works for everyone the first time as much as possible. If that means more discussion, then that is what is required. Eventually, as with other things, I'm sure we can come to an agreement with time.</div></div><div dir="ltr" class="gmail_msg"><div dir="ltr" class="gmail_msg"><br class="gmail_msg"><br class="gmail_msg">- Logan</div></div><div dir="ltr" class="gmail_msg"><br class="gmail_msg"><div class="gmail_quote gmail_msg"><div dir="ltr" class="gmail_msg">On Mon, Mar 20, 2017 at 9:07 PM Helge Heß 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"></div><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br class="gmail_msg">
<br class="gmail_msg">
unsurprisingly for me there is a heated discussion on this in the pull request. I thought I bring it back over here:<br class="gmail_msg">
<br class="gmail_msg">
<a href="https://github.com/swift-server/work-group/pull/76" rel="noreferrer" class="gmail_msg" target="_blank">https://github.com/swift-server/work-group/pull/76</a><br class="gmail_msg">
<br class="gmail_msg">
I wonder where this is going. I mean all those discussions are nice and valuable, but someone eventually has to do the work, right? :-)<br class="gmail_msg">
<br class="gmail_msg">
My understanding is that there is a goal to have that essentially ready in summer / for Swift 4, right? How is this going to happen? Is IBM and/or Apple going to provide a reference implementation and the others can use it or not?<br class="gmail_msg">
<br class="gmail_msg">
hh<br class="gmail_msg">
<br class="gmail_msg">
> On 16. Mar 2017, at 21:56, Chris Bailey 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">
> We're now at the point that we have broad agreement on the general approach to building a set of HTTP APIs, and we're starting to get down to the next level of detail which is likely to be more iterative. As such we'll be having more regular meetings and starting to have working designs in Google Docs and GitHub.<br class="gmail_msg">
><br class="gmail_msg">
> We'll therefore start scheduling the next meeting immediately after the previous one. Please use the Doodle Poll below to show your availability - dates between March 27th and April 7th are available.<br class="gmail_msg">
> <a href="http://doodle.com/poll/nfmepruih5nr9p2g" rel="noreferrer" class="gmail_msg" target="_blank">http://doodle.com/poll/nfmepruih5nr9p2g</a><br class="gmail_msg">
><br class="gmail_msg">
> Thanks,<br class="gmail_msg">
><br class="gmail_msg">
> Chris<br 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">
> _______________________________________________<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></div></div>