15:21:00flip214when swank starts to listen, SETUP-SERVER calls an announce function and passed the TCP port in - but not the address it is listening on.
15:21:22flip214This makes a difference when ::1 is bound but the client tries to reach 127.1 ...
15:22:16flip214so a) should the announce function receive the TCP address as well (requiring either new functions or a second return value to LOCAL-PORT)
15:22:35flip214or b) should we communicate it via a special
15:22:59flip214or c) should the client "just" test both? what if it tries a.b.c.d, but ::anything would be correct?
15:23:15flip214I guess a) would be the best solution, but I'd like to hear some feedback.
15:30:11flip214d) CREATE-SERVER could accept an ANNOUNCE-FN argument (like SETUP-SERVER) that I could use - SETUP-S doesn't take an INTERFACE argument any more