> *Subject:* Re: [twsocket] More friendly winsock exceptions
> *From:* Stephen Dickason <sdicka...@elcb.co.za>
> *To:* ICS support mailing <twsocket@lists.elists.org>
> > The bind error is the most annoying, ...
> Definitely.
The new friendly exceptions ar
> Some of my applications actually parse that last message to look-up the
> address and port for a more friendly response to the user.
I would like that in my programs.
> And that is the real issue here, are more friendly errors a benefit to ICS,
> or will
> they frustrate developers that
> We also have a long term problem with the OnError event. It skips raising
an exception and
> simply calls the event without the actual error information being
available, and in a few
> places continues program flow, not sure how useful this is, it probably
confuses users.
The OnError event
> IMO the correct way to handle this enhancement is to extend
> ESocketException to add more fields with more details about the
> exception, without changing the current error message.
In principle I agree, although I'd add an option for the friendly error
message to be the default instead of
> 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
