<html><body><p><tt><font size="2">> > Furthermore, if not all underyling TLS libraries support vectored IO, then having that </font></tt><br><tt><font size="2">> > as input to onReceive/onSend doesn't make sense.<br>> <br>> This I can’t follow. If OpenSSL supports this, it is absolutely worth supporting that in the API? </font></tt><br><tt><font size="2">> OpenSSL will almost always be in use in server deployments - </font></tt><br><tt><font size="2">> if that gets faster it matters a lot?<br></font></tt><br><tt><font size="2">Fair point.</font></tt><br><br><tt><font size="2">My suggestion is maybe we can overload the onReceive/onSend functions so that they can receive both Data and iov. </font></tt><br><tt><font size="2">That way we can start with the simple (known) implementation of Data and then iterate over the protocol with support for iov.</font></tt><br><br><tt><font size="2">Thoughts?</font></tt><br><br><br><br><br><br><img width="16" height="16" src="cid:1__=8FBB0A67DFCD03AE8f9e8a93df938690918c8FB@" border="0" alt="Inactive hide details for Helge Heß via swift-server-dev ---03/31/2017 10:19:04 AM---On 31 Mar 2017, at 16:55, Gelareh Taban <g"><font size="2" color="#424282">Helge Heß via swift-server-dev ---03/31/2017 10:19:04 AM---On 31 Mar 2017, at 16:55, Gelareh Taban <gtaban@us.ibm.com> wrote: > Furthermore, if not all underyl</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Helge Heß via swift-server-dev <swift-server-dev@swift.org></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">swift-server-dev <swift-server-dev@swift.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">03/31/2017 10:19 AM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [swift-server-dev] Draft proposal for TLS Service APIs(pleasereview)</font><br><font size="2" color="#5F5F5F">Sent by: </font><font size="2">swift-server-dev-bounces@swift.org</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><tt><font size="2">On 31 Mar 2017, at 16:55, Gelareh Taban <gtaban@us.ibm.com> wrote:<br>> Furthermore, if not all underyling TLS libraries support vectored IO, then having that as input to onReceive/onSend doesn't make sense.<br><br>This I can’t follow. If OpenSSL supports this, it is absolutely worth supporting that in the API? OpenSSL will almost always be in use in server deployments - if that gets faster it matters a lot?<br><br>For SecureTransport you would just need to merge the buffers before handing them over. That is the same you expect from your API consumer today.<br><br>hh<br><br>[attachment "signature.asc" deleted by Gelareh Taban/Austin/IBM] _______________________________________________<br>swift-server-dev mailing list<br>swift-server-dev@swift.org<br></font></tt><tt><font size="2"><a href="https://lists.swift.org/mailman/listinfo/swift-server-dev">https://lists.swift.org/mailman/listinfo/swift-server-dev</a></font></tt><tt><font size="2"><br></font></tt><br><br><BR>
</body></html>