[swift-server-dev] Prototype of the discussed HTTP API Spec

[Chris Bailey]

This has clearly sparked a lot more discussion about the API surface, 
which is a good thing. Equally we need to progress this towards having a 
concrete solution.

Whilst I agree with Paulo's proposal to iterate through the types and APIs 
over the coming weeks, I believe we need to do this on a working 
implementation rather than abstract definitions (even if those definitions 
are code).

What's in the carlbrown/HTTPSketch repo is the result of our last round of 
abstract discussions, plus a couple of very minor modifications - we could 
revert those before moving over to swift-server, but there's probably 
little value in that as we're going to crawl through everything that's 
there and debate it all anyway!

As part of moving it over, I'll also try to capture a list of all of the 
discussion points from the mailing list and from Paulo's README so that we 
make sure we discuss and check off each item.

Chris




From:   Michael Chiu via swift-server-dev <swift-server-dev at swift.org>
To:     Carl Brown <carl.brown.swift at linuxswift.com>
Cc:     Paulo Faria via swift-server-dev <swift-server-dev at swift.org>
Date:   27/05/2017 09:13
Subject:        Re: [swift-server-dev] Prototype of the discussed HTTP API 
Spec
Sent by:        swift-server-dev-bounces at swift.org



Hi Carl


>                This email thread isn’t about an API proposal. It’s about 
a prototype implementation of an API that was already proposed and 
discussed a month and a half ago.  The prototype isn't a full-featured 
framework like Vapor or Kitura, but it does actually work and it even has 
XCTests with decent (>75%) code coverage. 

I see, I was confused by the email contents instead of reading the subject 
and thought we are finally implementing some code. TBH, I don’t see any 
reason why this should not move to swift-server on github, It sounds a 
good start to me. 
Thank you guys’ hard work for building it.

>                Also, please note that I didn’t play any part in 
proposing this API back in March/April - it’s not “Carl’s proposal.”  I 
just took the existing API that the group had previously discussed and 
implemented enough of it so that we could measure the utility and 
performance of the API as proposed and so that we could have better 
informed discussions about potential alternatives. 

You’re right. it was Johannes’ proposal, I’m so sorry for that.

Michael.

_______________________________________________
swift-server-dev mailing list
swift-server-dev at swift.org
https://lists.swift.org/mailman/listinfo/swift-server-dev



Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-server-dev/attachments/20170527/962fe3f1/attachment.html>