Artifact dbb639a5e242b2cee1271c345633818ca749aea102cd912e9af4c11a8315e1d1:
- File
src/exceptions/OFBindDDPSocketFailedException.m
- 2022-10-22 18:32:59 — part of check-in [707206e796] on branch appletalk — OFDDPSocket: Bind with network, node & port (user: js, size: 1817) [annotate] [blame] [check-ins using]
-
2022-10-22 21:58:55
— part of check-in
[b62cca0487]
on branch trunk
— Add support for AppleTalk DDP sockets
Tested between a Linux and NetBSD machine. (user: js, size: 1817) [annotate] [blame] [check-ins using]
-
2022-10-26 22:17:16
— part of check-in
[8866fca78d]
on branch trunk
— OFDDPSocket: Revert not including node in bind
Looking at the NetBSD code (/usr/src/sys/netatalk/ddp_usrreq.c), it
seems to be allowed to specify a node after all, contrary to what
atalk(4) says. Looking at the Linux code (net/appletalk/ddp.c) seems to
confirm this. (user: js, size: 1817) [annotate] [blame] [check-ins using] -
2022-10-31 21:35:13
— part of check-in
[e70159ebb5]
on branch trunk
— Restore AppleTalk support
It is possible to use DDP sockets on macOS and Windows after all.
The commits following this will introduce the necessary changes. (user: js, size: 1817) [annotate] [blame] [check-ins using]