<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I would suggest against implementing HTTP protocol directly unless you are willing to tackle complexities like TLS, HTTP/2 and even supporting other languages directly. We can implement the FastCGI protocol and let the user piece together the final website using a purpose-built Web server software that implements all above like nginx.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">FastCGI is a mature protocol so it is safe and stable to track (while HTTP is receiving quick development in both HTTP/2 and TLS layers), has the benefit of being able to be executed on a separate machine from the Web server so vulnerability can be isolated and would be a natural fit for load balancing, and is widely used in hosting other languages like PHP, Python and Perl.</div><div id="AppleMailSignature"><br>Sent from my iPad</div><div><br>On Dec 8, 2015, at 00:24, Lukas Stabe via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8">The [Nest project](<a href="https://github.com/nestproject/Nest" class="">https://github.com/nestproject/Nest</a>) seems to aim to be something like this.<div class=""><br class=""></div><div class="">While I agree that a Rack/WSGI/Plack equivalent would be benificial to have, I don’t think it fits the current goals of the stdlib (providing basic data structures and algorithms) for now.</div><div class=""><br class=""></div><div class="">Lukas</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 07 Dec 2015, at 16:27, John Siracusa via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">The very first thing I considered writing in Swift is an implementation of Plack (<a href="http://plackperl.org/" target="_blank" class="">http://plackperl.org/</a>). It seems like every language benefits from having something like this (Rack in Ruby, WSGI in Python, etc.), even if only to insulate web applications from the web server implementation. I'm not sure if a language benefits from having 20 things like this, at least in the long run…<div class=""><br class=""></div><div class="">-John</div><div class=""><br class=""></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, Dec 7, 2015 at 9:08 AM, Coen Wessels via swift-evolution <span dir="ltr" class=""><<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">Since the linux port is available everybody is implementing their own HTTP server framework <a href="https://github.com/search?utf8=%E2%9C%93&q=http+language%3Aswift" target="_blank" class="">https://github.com/search?utf8=✓&q=http+language%3Aswift</a>. I think introducing a default http web server protocol(swift protocol) in the stdlib, something like rack(ruby) or plug(elixir), would prevent a lot of fragmentation in interfaces.</div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=zlf4dR0nvlJYLhwcLLjLQ-2FCecgKliMR5YhsxHxM-2Fcowa8evoJSD02kJtgKZfI7KBAWaEJ5BnjfHVTAHmCJ1HwN6zqEMg9PWi0nCOj8jvgABUaMrg70o3z-2BaZty6BXkF1bthPWb1DQmZe1ARCTmoelYHhP58a5hCmcl7F-2BEoj9zS2UBN7A7W8TtImq95qN7Wc4Z6jUdvvPiSPTsL-2FDThtn2Ih4sBf-2F3cRrVtvqdrpPX0-3D" alt="" width="1" height="1" border="0" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important" class="">
<br class="">_______________________________________________<br class="">
swift-evolution mailing list<br class="">
<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a><br class="">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
<br class=""></blockquote></div><br class=""></div></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=WzenSAN-2FiuX4NjI8OMkm0C8OpI7loozbOyGjfevETZsU3AMXI2dZCz3ujF-2FJuCLk98DkIl-2B5qrHGFzUMytqM-2FWa3tR-2BB-2BG0hykMBvkV5LeFNYnwJT1UZS8zcyV2ctYFfxIlmF6hOLfWYccs8DlZfKfITVANp-2Fk7wDM39dBaxAymMJHxVGE3infqH4sDlXAOAK9b-2B8-2FDL9FODCv3R8Zc3QoSMIN9ZXYFAOJNUYFzmkOA-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" class="">
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><br class=""></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=37YQSuyAAkYNrBa3dpH9qAdiTZku-2BF62gu95ZKLoar82Vo7TpaAWcCt5XOY2DE5Wgt2STDzk-2F-2FBI6neRPOk-2BT-2Fc1WksCIPWJyhSCJn3E4Mul74v2-2BhZyfArgjs6gbST2jK-2BHxdOEI2kdZ4r2YxXpIle1f-2Bj6dX2Y1GhtYRsOKcXHc9MkjFiWT-2B-2By0rCc7qJp2u0kJrL2Sq-2BYKrInCDygVQ-3D-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;">
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>