On 2010-11-16 17.45, Tim Peierls wrote:
> What's wrong with proliferation of resources? Changing a password and
> exporting to a database sound like two very different things; wouldn't
> you *want* to expose them as different resources?
I agree, that's how I do it. A GET on /contacts//changePasswo
What's wrong with proliferation of resources? Changing a password and
exporting to a database sound like two very different things; wouldn't you
*want* to expose them as different resources?
--tim
On Tue, Nov 16, 2010 at 7:56 AM, Daniele Dellafiore wrote:
> Hi. I have this design dilemma.
>
> I
Hi. I have this design dilemma.
I have a ContactResource mounted at /contacts/${code}
Now I have a couple of opeartions, like "change password" and "exportToSap".
Each of them is a Post operation, so I think I can map both on the
same URL cause they are related to that specific Contact resource.
3 matches
Mail list logo
