Your CGI script loops as long as the socket is open: 
    while ( $line = <$sock> ) {
        push @output, $line;
    }
    print $sock "BYE\n";

[download]

Your server doesn't close the connection until it gets a "BYE" from the client, but the client doesn't send a "BYE" until the server closes the connection. An easy solution would be to add a numeric or some other response from the server that marks the end of a command's output: 

# In the server script
sub process {
   ...
           print $new_sock <<EOF;
OK
$output
123 End of output
EOF
}

# In the CGI script
sub execute
{
    while ( ($line = <$sock>) !~ /^123/ ) {
        push @output, $line;
    }
    print $sock "BYE\n";
}

[download]

-Matt

In reply to Re: Socket programming & CGI hell by DrManhattan
in thread Socket programming & CGI hell by TQuid

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.