[
Lists Home |
Date Index |
Thread Index
]
On Thursday 27 December 2001 11:41 pm, Don Park wrote:
> While XML-based Linda service network can be used for SOAP service
> lookup, I would go one step further so that SOAP invocations and results
> become tuples, thus removing the need for SOAP consumers to find
> providers entirely: you send SOAP invocation to Linda and wait for
> result to 'bubble' without being concerned about who provided the
> service (billing layer will of course have to exists for commercial
> services).
Right... but this constrains the application to effectively "compute"
services. Linda was great for coordinating things like the seti@home kind of
work, or cracking RSA codes, where each consumer could bite of a chunk, chew
on it, and then spit the result back into the tuple space.
The thing is that as soon as things get much more complicated than this, the
tuple space model requires real programming... in a somewhat unfamiliar
manner (programs would often resemble state machines where each tuple is
tagged with the state). Each additional layer of abstraction tends to hide
the tuple space behind application semantics/models.
The associative-memory aspects and coordination aspects certainly don't need
XML either.
Again, I can see a (fairly large) group of problems that tuple-spaces are
ideal for, but I haven't seen the real killer app in Ruple yet...
|
