• Torarin Hals Bakke <torarind gmail.com> Aug 22 2010

Torarin Hals Bakke <torarind gmail.com> writes:

--0016e6d97108153dc9048e689721
Content-Type: text/plain; charset=ISO-8859-1

Perhaps Socket.shutdown() in std.socket should throw an exception in case of
an error? Unlike close(), it may fail before you are done with the socket.
One may, for instance, want to wait for a confirmation message from the
client after sending the FIN packet with shutdown(SocketShutdown.SEND). If
the client disconnected, POSIX shutdown() can inform you with erro ENOTCONN.

--0016e6d97108153dc9048e689721
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Perhaps Socket.shutdown() in std.socket should throw an exception in case o=
f an error? Unlike close(), it may fail before you are done with the socket=
.<div>One may, for instance, want to wait for a confirmation message from t=
he client after sending the FIN packet with shutdown(SocketShutdown.SEND). =
If the client disconnected, POSIX shutdown() can inform you with erro ENOTC=
ONN.</div>

--0016e6d97108153dc9048e689721--