It looks like your FIFO is only used for the child to speak to the parent. Would a regular pipe serve better? It would be faster.

while (my $connection = $listen_socket->accept)
{
    my ($pid, $line, $in, $out);
    pipe $in, $out or die $!;
    if ($pid = fork) {   
        close($out);
        warn localtime(time),
             " Connection recieved ... ",
             $connection->peerhost,
             $/;
        $connection->close();
        # microsleep till the kid's awake
        do { select undef, undef, undef,.001} until kill 0, $pid;     
+ 
        while(<$in>){$_ =~ s/a-z/A-Z/i;print $_;}
        close($in);
    }
    elsif (defined $pid){
        close($in);
        $listen_socket->close;
        while(<$connection>){print $out $_;};
        close($out);
        exit 0;
    }
    else {
        die "Error while forking: $@" unless defined $pid;
    }
}
[download]

There may be a lot more to do to make this work with your real application, particularly if there is to be more than one connection at a time. In that case, the parent will need to listen on the socket and several pipes at once.

After Compline,
Zaxo

---

---

• 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.