Without really knowing how you have implemented your server, I can give you the following advice if you are doing non-blocking I/O with the help of IO::Select or IO::Poll:

After getting a read-event on the socket, you'll go to do your sysread, and you'll get back 0 bytes. That means the client closed the socket. The following code snippet illustrates:

my $bytes_read = $socket->sysread($buf, $max_read_len);

if (not defined $bytes_read)
{
    print "ack!  error on the socket\n";
}
elsif ($bytes_read == 0)
{
    print "the socket was closed\n";
}
else
{
    print "woo hoo!  I read $bytes_read bytes from the socket...\n";
}

[download]

You might want to look at this node for more info:
Detecting a closed socket

HTH

--
3dan

In reply to Re: Detecting disconnection from client using IO::Socket Objects. by edan
in thread Detecting disconnection from client using IO::Socket Objects. by Abroxa

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.