Artifact ff93d36ccbe9a2099926b5abb380240be88e8a79cc7e1778a9413f39a0fd3186:
- File
src/OFDNSResolver.m
- 2020-04-18 20:43:08 — part of check-in [321f4c67a4] on branch trunk — OFDNSResolver: Retry with TCP if TC is set (user: js, size: 32915) [annotate] [blame] [check-ins using]
-
2020-04-25 13:40:50
— part of check-in
[424fb54efd]
on branch trunk
— Remove OFIPStreamSocket
This was a bad idea, as while SCTP can be used via the byte
stream-oriented API, it will still work in messages. But OFStream is not
afraid of breaking up and reassembling reads, as it is meant for byte
streams. Therefore, implementing SCTP as a subclass of OFStream would
degrate it to a stream-oriented socket instead of a message-oriented
socket, rendering one of the main features of SCTP void. (user: js, size: 32915) [annotate] [blame] [check-ins using]