[plt-scheme] Limiting Concurrent Connections to Web Server

From: Robby Findler (robby at eecs.northwestern.edu)
Date: Mon Jan 12 14:24:40 EST 2009

On Mon, Jan 12, 2009 at 1:02 PM, Jay McCarthy <jay.mccarthy at gmail.com> wrote:
> On Mon, Jan 12, 2009 at 11:03 AM, Robby Findler
> <robby at eecs.northwestern.edu> wrote:
>> Continuing on this dead horse down just one more block: if it were
>> important, you could even build this abstraction directly into the
>> servlets, since it doesn't require the more powerful custodian that
>> the dispatchers seem to have (or if dispatchers can be killed, you can
>> improve the abstraction to cope with that).
> I'm pretty sure it would work as written, actually.

Right. Didn't mean to say it wouldn't. Only that you don't need a
dispatcher (server?) custodian in order to do this. Maybe you don't
care, tho. :)

> The custodians have this structure:
> (root
>  (server (servlets servlet_1 ... servlet_n)
>             (connections conn_1 ... conn_n)))
> The first request to a servlet starts off under the connections, but
> when the server realizes it is a servlet, it creates a new custodian
> with a different parent to evaluate the module in. If the module
> created the limit manager, then the subsequent conns would be able to
> communicate with it.

Posted on the users mailing list.