Jason Sibre wrote:
> Hey folks,
>
> I have something here that some of you might find useful.  It's a (probably
> poorly named) module for handling tasks in a separate thread, and storing
> the result until the original thread comes back to get it.  It isn't a tuple
> space, but it was -in part anyway - inspired by the tuple space discussion
> on this list a several months back relating to approaches on handling long
> running requests.

I wanted to say thanks for this, Jason. I still haven't had the time to
take a close look at the code, but this is a good building-block to have
at hand. When I get a bit of free time, I'll play the friendly critic
and give your code a test-drive.

My CMS project has a need for a defered-request system, but I want it to
scale and distribute across multiple processes/servers, so I'm going to
try the tuple-space approach. It makes development a bit tougher -- it's
hard (for me) to re-imagine a 'monolithic' program in terms of multiple
processes running on multiple machines -- but I have hopes that it will
work for me in the long run.

Anyway, thanks, and I look forward to a closer read later on.

-- Graham