[plt-scheme] Limiting Concurrent Connections to Web Server

From: hendrik at topoi.pooq.com (hendrik at topoi.pooq.com)
Date: Sat Jan 17 08:29:06 EST 2009

On Fri, Jan 16, 2009 at 10:23:48AM -0500, Henk Boom wrote:
> 2009/1/16 Jay McCarthy <jay.mccarthy at gmail.com>:
> > On Fri, Jan 16, 2009 at 8:02 AM, Henk Boom <lunarc.lists at gmail.com> wrote:
> >> It's not that I want to drop all connections after the first 5, it's
> >> just that if the connection is cancelled by the other party after it
> >> queues up, there's no point in letting it start.
> >
> > One implication of the release rules I wrote earlier, is that a
> > problem with the connection won't be noticed until it is written to,
> > which is /after/ the work has been done. I'm not sure how (or if I'd
> > want to) have another thread monitoring the connection port to see if
> > it is active, it doesn't look like there is anything in scheme/tcp
> > that does that.
> I see what you mean. This could even be seen as a feature, for
> requests which result in side effects.

in which case you'd want all of the side effects top be performed, or 
none of them, but not just some?

-- hendrik

Posted on the users mailing list.