<html><body><p><tt><font size="2">> > > > Like the followings:<br>> > > > func tlsWrite(buffer: Collection<UInt8>) throws<br>> > > > func tlsWritev(vectors: Collection<iovec>)<br>> > > ><br>> > > > If it is possible it will be very helpful since<br>> > > > 1) it is very swifty and user friendly<br>> > > > 2) vectorIO could significantly reduce the overhead to merge fragments of bytes into a single buffer.<br>> > ><br>> > > +1 on vectors.<br>> > ><br>> > <br>> > +1 on need to make it more Swifty.<br>> > <br>> > What is the advantage of using vectored IO for TLS service?<br>> <br>> ? Less copying and/or using a single system call for a buffer.<br></font></tt><br><br><tt><font size="2">[g] Agreed about general efficiency, but with TLS, you would need a different context for each of these streams. </font></tt><br><tt><font size="2">Coordinating the appropriate streams and associated contexts would be complex and perhaps it's better managed at a higher level?</font></tt><br><tt><font size="2">That way we can have the low level TLS service taking care of one stream/contexts and have transport or even higher level still, </font></tt><br><tt><font size="2">deal with handling of multiple streams.</font></tt><br><br><br><BR>
</body></html>