Re: [service-orientated-architecture] RESTful lightbulb

[Anne Thomas Manes]

The resource in question, here, is the Trade.  When the Trade is confirmed, you PUT "confirmed", and you POST to PartyA and PartyB (also resources) a link to the Trade resource.

Anne

On 7/3/06, Steve Ross-Talbot <[EMAIL PROTECTED]> wrote:

Let me provide a real word usecase similar to Ashley's one.

The DTCC manage confirmations of derivative trades. Trades occur
between two parties - PartyA (the bank) and PartyB the counterparty.
Occasionally trades are assigned to a third party (PartyC).

Trades can be submitted by either PartyA or PartyB (the order does not
matter).
DTCC on receipt of a valid trade from two parties send out a
notification to
both parties that the trade is "Confirmed" (the state change equiv to
married after
a "marry"). PartyA and PartyB are distinct.

How does REST handle such a notification?

It gets slightly mroe complex is the trade is assigned. After
submitting the assignment
(PartyA, partB and PartyC). A notification is sent to all three that
the assignment is
"Confirmed".

How does REST handle tri-party agreements of this nature?

Cheers

Steve T

On 3 Jul 2006, at 09:26, Jan Algermissen wrote:

>
> On Jul 2, 2006, at 11:56 PM, Ashley at Metamaxim wrote:
>
> > How in REST would you handle something like "marry" where a single
> > event causes the states of two resources (two people) to change
> > (they both become married). Would you need two PUTs? If so, how do
> > you ensure that the two PUTs are atomic: both succeed or both fail?
> >
>
> Interesting one!
>
> Clarification question: are the two persons locally managed or would
> one need a distributed transaction to update both?
>
> Jan
>
> > Thanks
> > Ashley
> >
> >
>
>
>

__._,_.___

---

YAHOO! GROUPS LINKS

•  Visit your group "service-orientated-architecture" on the web.
   
•  To unsubscribe from this group, send an email to:
   [EMAIL PROTECTED]
   
•  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

---

__,_._,___