|
Anne wrote:
> 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.
The analogue in the "marry" case would be to PUT a
"marriage contract" and POST a link to the two people involved. So are we
obliged to model "marriage contract" to make the solution work? In this case it
seems that the implementation is driving the modelling, which is not good in my
book.
Consider a "transfer" of $100 from Account1 to
Account2. Do we have to have the "transfer" as a resource?
Also, this solution implies that PUT and POST are
complementary (i.e., in general, you need to use both) rather than alternative
(i.e., you choose whether you want to use PUT or POST). Is that the
case?
Rgds
Ashley
SPONSORED LINKS
YAHOO! GROUPS LINKS
|
- Re: [service-orientated-architecture] RESTful lightbul... Ashley at Metamaxim
- Re: [service-orientated-architecture] RESTful lig... Anne Thomas Manes
- Re: [service-orientated-architecture] RESTful... Ashley at Metamaxim
- Re: [service-orientated-architecture] RES... Eric Newcomer
- Re: [service-orientated-architecture]... Mark Baker
- Re: [service-orientated-architec... Dan Creswell
- Re: [service-orientated-arch... Mark Baker
- Re: [service-orientated-... Dan Creswell
- Re: [service-orientated-architec... Eric Newcomer
- Re: [service-orientated-arch... Mark Baker
- Re: [service-orientated-architecture] RESTful... Jan Algermissen
