It's annoyed me for many years that many internet applications give unfriendly errors, sometimes just five digit error codes, sometimes terse messages.
Specifically, when starting a server on an address and port that is being used, the current ICS exception is: Address already in use (#10048 in Bind) I propose to change this to: Another server is already listening on 192.168.1.120:80 so you actually trace (maybe) the offending application. This is particularly annoying with MultiListen servers which say: Listening socket index #1 Address already in use (#10048 in Bind) and you've no idea which address relates to which index. Some of my applications actually parse that last message to look-up the address and port for a more friendly response to the user. And that is the real issue here, are more friendly errors a benefit to ICS, or will they frustrate developers that already parse them into something better. Or like me, do you rarely bother? The bind error is the most annoying, but others could be made more friendly. The LastError property will still give the real winsock error you want to report it. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
