Kendall Grant Clark wrote:

>>>>>>"graham" == Graham Fawcett  writes:
>
>
>   graham> Actually, it would be very interesting, and probably quite
>   graham> simple, to write a Quixote-based tuple space engine: a
>   graham> bare-bones write/take interface with a pluggable backend
>   graham> (in-memory, ZODB, Berkeley, ...).  Would anyone be interested in
>   graham> such a thing?
>
> REST is sometimes likened to tuplespaces, since both are kinds of
> coordination language (well, roughly).

I don't claim to understand REST very deeply, but I can see the similarities.
What seems to be the largest difference is that tuple spaces _tend_ to be
associative by query, and the same query could (almost certainly will) return a
different object representation every time. So even a RESTful implementation
would probably have only 'write' and 'take' URIs, woudln't it?

>  I suspect, though I haven't thought
> enough about this yet, that you could at least crudely map a tuplespace
> interface onto HTTP in some interesting ways.

Well, the implementation I just posted to the list is pretty crude indeed, but
it has a certain charm. ;-) I would be interested in what, in your opinion,
might constitute a more RESTful approach.

Regards,

-- Graham