<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Thanks for sharing this!<div class="">Nice to read about the details of the implementations and the reasons behind the decisions that you and your team took while making BlueSSLService.<div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><table cellspacing="0" cellpadding="0" style="background-color: rgb(255, 255, 255); padding: 0px; margin: 0px; font-family: 'Lucida Grande', sans-serif; font-size: 12px; color: rgb(176, 176, 176);" class=""><tbody class=""><tr style="margin: 0px; padding: 0px;" class=""><td style="font-family: arial, sans-serif; margin: 0px; padding: 0px; white-space: nowrap;" class=""><span style="color: rgb(73, 79, 80); font-family: 'Helvetica Neue', san-serif; font-size: 14px; white-space: normal;" class="">—<br class=""></span><span style="color: rgb(0, 0, 0); font-family: Helvetica; white-space: normal;" class="">Cheers,<br class="">Alfredo Delli Bovi</span></td></tr></tbody></table></div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 13 Dec 2016, at 16:50, Gelareh Taban via swift-server-dev <<a href="mailto:swift-server-dev@swift.org" class="">swift-server-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><p class="">To prepare for the Security Group meeting tomorrow, we put together a quick write up of our experience when coming up with consistent Swift APIs for TLS support in Kitura.<br class=""><br class=""><a href="https://developer.ibm.com/swift/2016/12/13/securing-kitura-cross-platform-challenges/" class="">https://developer.ibm.com/swift/2016/12/13/securing-kitura-cross-platform-challenges/</a><br class=""><br class="">Gelareh<br class=""><br class=""><br class=""><span id="cid:1__=8FBB0A1BDFC53FE88f9e8a93df938690918c8FB@"><graycol.gif></span><font color="#424282" class="">Bill Abt via swift-server-dev ---11/12/2016 10:01:00 AM---I absolutely agree. Why re-invent the wheel? Existing libraries that would be chosen are most like</font><br class=""><br class=""><font size="2" color="#5F5F5F" class="">From: </font><font size="2" class="">Bill Abt via swift-server-dev <<a href="mailto:swift-server-dev@swift.org" class="">swift-server-dev@swift.org</a>></font><br class=""><font size="2" color="#5F5F5F" class="">To: </font><font size="2" class="">Chris Lattner <<a href="mailto:clattner@apple.com" class="">clattner@apple.com</a>></font><br class=""><font size="2" color="#5F5F5F" class="">Cc: </font><font size="2" class="">Swift Server Dev <<a href="mailto:swift-server-dev@swift.org" class="">swift-server-dev@swift.org</a>></font><br class=""><font size="2" color="#5F5F5F" class="">Date: </font><font size="2" class="">11/12/2016 10:01 AM</font><br class=""><font size="2" color="#5F5F5F" class="">Subject: </font><font size="2" class="">Re: [swift-server-dev] Crypto Library</font><br class=""><font size="2" color="#5F5F5F" class="">Sent by: </font><font size="2" class=""><a href="mailto:swift-server-dev-bounces@swift.org" class="">swift-server-dev-bounces@swift.org</a></font><br class=""></p><hr width="100%" size="2" align="left" noshade="" style="color:#8091A5; " class=""><br class=""><br class=""><br class=""><tt class="">I absolutely agree. Why re-invent the wheel? Existing libraries that would be chosen are most likely “battle tested and proven”. To redo all that in Swift seems to me to be a waste of valuable time. There’s a lot more other work that needs to be done to make server side Swift successful and if that means reusing and leveraging existing “C” code, so be it.<br class=""><br class="">-Bill Abt<br class=""><br class="">> On Nov 10, 2016, at 3:02 PM, Chris Lattner via swift-server-dev <<a href="mailto:swift-server-dev@swift.org" class="">swift-server-dev@swift.org</a>> wrote:<br class="">> <br class="">> <br class="">>> On Nov 8, 2016, at 2:18 PM, Helge Heß via swift-server-dev <<a href="mailto:swift-server-dev@swift.org" class="">swift-server-dev@swift.org</a>> wrote:<br class="">>> <br class="">>> On 8 Nov 2016, at 16:45, Chris Bailey via swift-server-dev <<a href="mailto:swift-server-dev@swift.org" class="">swift-server-dev@swift.org</a>> wrote:<br class="">>>> Whilst there's legitimate debate on the use of C vs. Swift for HTTP parsing, I think the situation for the security libraries in general is more clear.<br class="">>> <br class="">>> This is really a bit off topic but I disagree with that. Either you:<br class="">>> a) are OK with C libs and deal with it<br class="">>> b) deal with C libs as a temporary measure but the goal is Swift<br class="">>> c) reject C libs from the start<br class="">> <br class="">> Just my personal opinion, but I don’t see why “pure swift” is a goal or even interesting to thing about. The goal should be provide expressive and natural Swift APIs for server development tasks. The implementation should not show through that API.<br class="">> <br class="">> If (and only if) there is some advantage to rewriting C code in Swift (e.g. for performance, memory, correctness, or capability reasons) then it is certainly interesting to talk about that of course.<br class="">> <br class="">> A relevant comparison is to corelibs-foundation, which uses a significant amount of C code in its implementation. <br class="">> <br class="">> -Chris<br class="">> _______________________________________________<br class="">> swift-server-dev mailing list<br class="">> <a href="mailto:swift-server-dev@swift.org" class="">swift-server-dev@swift.org</a><br class="">> </tt><tt class=""><a href="https://lists.swift.org/mailman/listinfo/swift-server-dev" class="">https://lists.swift.org/mailman/listinfo/swift-server-dev</a></tt><tt class=""><br class=""><br class="">_______________________________________________<br class="">swift-server-dev mailing list<br class=""><a href="mailto:swift-server-dev@swift.org" class="">swift-server-dev@swift.org</a><br class=""></tt><tt class=""><a href="https://lists.swift.org/mailman/listinfo/swift-server-dev" class="">https://lists.swift.org/mailman/listinfo/swift-server-dev</a></tt><tt class=""><br class=""></tt><br class=""><br class=""><br class="">
</div>
_______________________________________________<br class="">swift-server-dev mailing list<br class=""><a href="mailto:swift-server-dev@swift.org" class="">swift-server-dev@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-server-dev<br class=""></div></blockquote></div><br class=""></div></div></body></html>