I just wrote a little multi-client server at work. It's in a request-response type of situation, i.e., the connections are short lived. Instead of forking, I used threads. One does need to share data explicitly. Some code samples are as follows: (any comments are appreciated, since it wasn't used in a heavy production environment, so I'm not sure how it scales.)
use strict;
use threads;
use threads::shared;
use IO::Socket;
# need to explicitly share variables across threads
our $something_to_share;
share($something_to_share);
my $socket = new IO::Socket::INET(
LocalPort=> 11023,
Proto => "tcp",
Listen => 10,
Reuse => 1)
or die "Socket could not be created, reason: $!";
while( my $client = $socket->accept() ){
threads->new(\&handler, $client)->detach();
}
exit(0);
sub handler{
my $client = shift;
#read request.
my $input = <$client>;
# do something, probably access the
# the shared variable $something_to_share;
# and send response back.
print $client "something for you.";
}
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.