[hunchentoot-devel] 'max-threads' behavior for Hunchentoot

[Faré]

Dear Hunchentooters,

here's my patch against the latest svn, de-xcvb-ified. That's what I'm
running at ITA, it seems to be passing the QRes precheckin. Can you
review, and apply if satisfactory?

Suggested commit message (from Scott McKay's svn commit):

    Extend Hunchentoot's 'one-thread-per-connection-taskmaster'
      to support 'max-threads' semantics, i.e., don't create
      a new thread if we've max out.

    Add a 'pooled-thread-per-connection-taskmaster' that will
      eventually use a thread pool, if profiling indicates.
    Fix the 'handle-incoming-connection' to implement the
      new behavior.
    Add a commented-out implementation of 'accept-connections'
      that might give better performance.  This needs to be
      discussed with the Hunchentoot maintainers.

    Address the review comments and discussions between Scott McKay
    and Hans Huebner, who is one of the H'toot maintainers.
    Also correctly issue HTTP 503 when the server runs out of threads.

(work by Scott McKay)

[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
Comparing oneself with Galileo or Einstein is certainly good for the ego —
provided one refrains from going into too much detail.  — John McCarthy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: max-foo-count.diff
Type: text/x-diff
Size: 36592 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/tbnl-devel/attachments/20100820/9f1717a2/attachment.diff>