At this time when an exception is thrown by a driver, be it network related or a server command, very few (if any) drivers provide direct information about the socket involved in the communication attempt. This can be important information to correlate a server event (presuming that server information is known) with a client side event.

It would greatly assist debugging efforts if exceptions raised by drivers, where a socket is known, to provide in the exception object the local IP and ephemeral port the socket was bound to (language permitting).