Re: Two uses of SOAP

Mark,

I'm somewhat of a lurker on this board, but I could see another use of SOAP
emerging over time: as a JCL for managing queued resources. Arguably, this
could fit into other of the other two divisions that you've set up, but the
RPC mechanism strikes me as being largely a client/server model where the
transactions are *roughly* synchronous (I'd describe these as moderately
coupled synchronous transactions), while application protocol frameworks are
in turn moderately coupled asynchronous transactions. A queue processing
system, on the other hand, is a weakly coupled aynchronous transaction - the
bindings on the SOAP objects make it possible to include multiple kinds of
entities in the same processing queue, while there is little correlation
between the time that a queued process is entered and the time that it's
processed (save that one must perforce come after the other).

As I said, it could very well be thought of as one of the other two, but
there are just enough differences in treatment and implementation that it
might be worth examining it as a separate division.

-- Kurt Cagle

----- Original Message -----
From: "Mark Baker" <mbaker@markbaker.ca>
To: <xml-dist-app@w3.org>
Sent: Friday, July 27, 2001 6:49 PM
Subject: Two uses of SOAP


> Just thought I'd write down more about the two uses of SOAP that
> I'm familiar with.  If you know of any other uses, I'd love to hear
> about them.  The more we know, the better the normative binding
> will be.
>
> http://www.markbaker.ca/2001/07/SoapUses/
>
> MB
>
>

Received on Saturday, 28 July 2001 04:21:15 UTC