There's a lot of guff and bluster around on this subject. And a lot of it comes from otherwise rational and reliable sources.
I needed a quick "concurrent clients" socket server for testing another piece of code against, so I knocked this up:
#! perl -slw
use strict;
use IO::Socket;
use threads;
our $ADDR ||= 'localhost:35007';
my $listener = IO::Socket::INET->new(
LocalAddr => $ADDR,
Listen => 5,
Reuse => 1,
) or die $^E;
while( my $client = $listener->accept ) {
async {
my($port, $iaddr) = sockaddr_in( getpeername( $client ) );
printf "From %s:%d: %s", join('.',unpack 'C4', $iaddr ), $port
+, $_
while <$client>;
close $client;
}->detach;
}
Simplistic, but it easily keeps up with 5 of these each fowarding the traffic from 100 monitored log files, so it didn't need to be any more complex.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
-
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.
|