Another post as I'd like to add a request for comments about what I've learned:

Result 1:
So HTTP::Daemon in essence behaves correctly, keeping connections alive on HTTP/1.1 requests, with the effect that this might block another client trying to connect.

This is a problem as long as HTTP::Daemon is single-threaded/non-forking, right? With a spawning HTTP::Daemon connection wrapper, although one connection might be doing keep-alive, there would be others idling waiting for connections, right?

Or do all the threads/forks still share a single socket, which is then blocked?

As said, I think I've seen this "blocking" behavior with forking Net::Server and assertively non-blocking AnyEvent::HTTPD based scripts - well, I think..
But forks sharing a single socket would explain this. But I again admit my limited understanding of socket workings.

Result 2:
Assuming that forks do not share a single (blocked) socket, a forking server might be able to serve keep-alive connections and closing ones side by side.
Adapting a ForkOnAccept concept from here, this is my result: 
#!/usr/bin/perl

use HTTP::Daemon;
use Data::Dumper;

my $d = HTTP::Daemon->new(
        LocalAddr => 'localhost',
        LocalPort => 4242,
        ReuseAddr => 1
) || die;

my $cnt;
# response loop
while (my $c = $d->accept) {
    my $pid = fork();

    # We are going to close the new connection on one of two condition
+s
    #  1. The fork failed ($pid is undefined)
    #  2. We are the parent ($pid != 0)
    if(!defined $pid || $pid == 0 ) {
        $c->close;
        print "Needs close: $pid\n";
        next;
    }

    # From this point on, we are the child.
    # $c->close;  # Close the listening socket (always done in childre
+n)

        # Handle requests as they come in
        while (my $request = $c->get_request) {
                print "Request:\n".Dumper($request);

                my $response = HTTP::Response->new( 200, 'OK');
                $response->header('Content-Type' => 'text/html'),
                $response->content("$cnt Working! (pid $pid)");
                $cnt++;

                # print "Response:\n".Dumper($response);
                $c->send_response($response);
        }
        $c->close;
        undef($c);
}

[download]
and guess what, it does work. (And on keep-alive connections the pid remains the same). Mh, although I get a lot of "Needs close: 0" messages from non-keep-alive clients. I think I need to think through fork()'ing again...

What's wrong/anything wrong with this design?

In reply to Re: Strange blocking issue with HTTP::Daemon by isync
in thread Strange blocking issue with HTTP::Daemon by isync

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.