On Wed, 18 Feb 2009, Leon Timmermans wrote:
On Wed, Feb 18, 2009 at 12:16 PM, Timothy S. Nelson
<wayl...@wayland.id.au> wrote:
On Wed, 18 Feb 2009, Leon Timmermans wrote:
The only difference I could see was that shutdown allows changing the
readability and writeability. While I agree that this functionality should
be exposed, (see my next update), I think that in the general case, .close()
plus the other stuff I've done should be sufficient. Maybe shutdown()
should be exposed somewhere, though.
You are missing one very important thing about shutdown: its effect is
on the connection and thus global. It also affects other processes
that share the same socket. close() OTOH is local. It only affects the
file descriptor, and only in the current process.
Ok. I agree that's significant. But, while I agree that the
difference is significant in *effect*, and is an essential part of the
difference between files and sockets, I thought the purpose of having a
somewhat abstract interface was to paper over differences like these.
Fundamentally, a recv() is a different call than a read(), but yet they're
similar enough in interface that it doesn't make a lot of difference from a
Perl point of view. Would a note in the documentation suffice to distinguish
between them?
:)
---------------------------------------------------------------------
| Name: Tim Nelson | Because the Creator is, |
| E-mail: wayl...@wayland.id.au | I am |
---------------------------------------------------------------------
----BEGIN GEEK CODE BLOCK----
Version 3.12
GCS d+++ s+: a- C++$ U+++$ P+++$ L+++ E- W+ N+ w--- V-
PE(+) Y+>++ PGP->+++ R(+) !tv b++ DI++++ D G+ e++>++++ h! y-
-----END GEEK CODE BLOCK-----
