Artifact 2284f227d59c58b293d826d91d29a7f5c26df7fa98e2a6e889fbe142bc5472e5:
- File
src/OFStreamSocket.h
- 2020-01-02 01:51:34 — part of check-in [c7f0229795] on branch trunk — Update copyright (user: js, size: 1155) [annotate] [blame] [check-ins using]
- 2020-01-08 02:29:37 — part of check-in [e7e1e1c6c5] on branch 1.0 — Merge branch 'master' into 1.0 (user: js, size: 1155) [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: 1155) [annotate] [blame] [check-ins using]