[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Socket error handling
From: |
Prochnow, Christian |
Subject: |
Socket error handling |
Date: |
Thu, 7 Nov 2002 23:01:03 +0100 |
User-agent: |
KMail/1.4.3 |
Hi List,
i'm wondering how one can do proper errorhandling using the throwException
error mode and the Socket class?
The SockException class which gets thrown should at least contain the error
code which caused the throw - without it it's simply useless.
A textual error message retrieved from the O/S is also usefull when passing
error messages down to the user and should be passed on each call to
Socket::error().
eg.
error(errBindingFailed,strerror(errno);
Using the SocketPort class there should also a way to retrieve the error which
caused the disconnect-event.
Regards,
Christian Prochnow
- Socket error handling,
Prochnow, Christian <=