For server side, one cares whether each connection can read or write, not the listening server socket. The listening socket does not read or write.
Let's do a simple testing. With the following client and server:
#server
use strict;
use warnings;
use IO::Socket;
use IO::Select;
my $sock = IO::Socket::INET->new(Proto=>"tcp", LocalHost=>"localhost",
+
Listen=>16, Reuse=>1, LocalPort=>3000)
|| die("Could not create socket!\n");
my $conn = $sock->accept();
my $sel = new IO::Select($sock);
if ($sel->can_read()) {
print "can read\n";
}
#client
use IO::Socket;
my $sock = IO::Socket::INET->new(
Proto=>"tcp",
PeerHost=>"Localhost",
PeerPort=>3000
) or die("Could not create socket!\n")
+;
print $sock "abcd\n";
Run perl -w server.pl in one window, then run perl -w client.pl in another window, nothing gets printed in the server window! run perl -w client.pl again, "abcd" gets printed. This is not what one will want.
change server code:
use strict;
use warnings;
use IO::Socket;
use IO::Select;
my $sock = IO::Socket::INET->new(Proto=>"tcp", LocalHost=>"localhost",
+
Listen=>16, Reuse=>1, LocalPort=>3000)
|| die("Could not create socket!\n");
my $conn = $sock->accept();
my $sel = new IO::Select($conn);
if ($sel->can_read()) {
print "can read\n";
}
The first time you run perl -w client.pl, server side knows that it can read, and prints "abcd". That's what one wants.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.