- From: bhaugen <linkage@interaccess.com>
- Date: Mon, 23 Dec 2002 09:47:23 -0600
- To: www-ws-arch@w3.org
I changed the subject because I'm feeling guilty about
hijacking Mark Baker's original subject, which I'd also
like to get back to.
But Geoff Arnold poses an interesting multiparty example:
> I don't know about "in use", but the canonical multiparty example
> is an auction, such as ContractNet. This only reduces to pairwise
> interactions if you trust the auctioneer to inform all parties,
> impartially and in a timely fashion, of every bid. In addition to
> being an interesting trust and non-repudiation issue (and getting
> into reliable messaging as well!) such a pairwise solution really
> doesn't scale very well. A multicast approach models the human
> notion of auction much better, and this pushes it into the
> multiparty zone....."
Ok, clearly auctions involve multiple parties.
In pairwise interactions:
Offerer interacts with Auctioneer.
Bidders interact with Auctioneer.
All Bidders can see bids posted by Auctioneer,
but do not interact with each other.
At the end, winning Bidder interacts with Offerer.
("Offerer" could also be "Auctioneer".)
Correct?
Do you have an example of a multicast implementation?
How do the interactions work? Are we getting into
virtual synchrony territory?
Received on Monday, 23 December 2002 10:50:00 UTC