On Wed, Aug 24, 2005 at 04:14:15PM -0400, Bob Showalter wrote:
> A connect() followed by a close() is just another form of this scenario. You
> need to have a client socket in order to detect the peer's closing the
> connection.
That clarifies things quite nicely. Thank you very much!
--
Mason
Bob Showalter wrote:
> I don't think there's any problem with IO::Socket. Even if accept
> returns a socket, you should receive an EOF on that socket when you
> try to read from it, which tells you that the peer has closed the
> connection. I think you just need to check for both situations: an
> e
Mason Loring Bliss wrote:
> On Tue, Aug 23, 2005 at 11:10:58AM -0400, Mason Loring Bliss wrote:
>
>> Hi, all! I'm learning about dealing with sockets in Perl, and I've
>> got a question about some unexpected behaviour exhibited by the
>> following test script.
>>
>> In the case where I open a co
On Tue, Aug 23, 2005 at 11:10:58AM -0400, Mason Loring Bliss wrote:
> Hi, all! I'm learning about dealing with sockets in Perl, and I've got a
> question about some unexpected behaviour exhibited by the following test
> script.
>
> In the case where I open a connection and then close it before
>
Hi, all! I'm learning about dealing with sockets in Perl, and I've got a
question about some unexpected behaviour exhibited by the following test
script.
In the case where I open a connection and then close it before
$socket->accept() is called, I'd except $socket->accept() to return undef,
but it
