[swift-server-dev] Next HTTP API meeting

Logan Wright logan at qutheory.io
Mon Mar 20 17:11:49 CDT 2017


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.

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

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.

- Logan

On Mon, Mar 20, 2017 at 9:07 PM Helge Heß via swift-server-dev <
swift-server-dev at swift.org> wrote:


unsurprisingly for me there is a heated discussion on this in the pull
request. I thought I bring it back over here:


I wonder where this is going. I mean all those discussions are nice and
valuable, but someone eventually has to do the work, right? :-)

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?


> On 16. Mar 2017, at 21:56, Chris Bailey via swift-server-dev <
swift-server-dev at swift.org> wrote:
> 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.
> 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.
>        http://doodle.com/poll/nfmepruih5nr9p2g
> Thanks,
> Chris
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
> _______________________________________________
> swift-server-dev mailing list
> swift-server-dev at swift.org
> https://lists.swift.org/mailman/listinfo/swift-server-dev

swift-server-dev mailing list
swift-server-dev at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-server-dev/attachments/20170320/f62b138f/attachment.html>

More information about the swift-server-dev mailing list