Hi Vincent, You got the semantics of your transaction resource right, but the name is just a bit ambiguous (IMHO) for someone not too familiar with your design.
Best regards, Jerome > -----Message d'origine----- > De : news [mailto:[EMAIL PROTECTED] De la part de Vincent > Envoyé : mardi 23 janvier 2007 00:19 > À : [email protected] > Objet : Re: Getting confused > > Hi Jerome, > > > > Your bank example looks good. I would just change the URI to > > '/transactions/accountCreations' to make it look more less like a > > verb/action which could be confusing when used with HTTP methods. > > I thought hard about this one. I concluded that using the > verb (createAccount) > was the right thing to do because it's the name of the > resource (transaction). > when I PUT /transactions/createAccount, I don't create an > Account resource, > I create a Transaction which name is 'createAccount'. > When I POST to /transaction/createAccount/123, > 'createAccount' is part of the > resource's name (the tx), not an indication of what to do > with the resource (as > it'd be the case with a url like 'account/createAccount'). > > -Vincent.
