Dan -
I don't know if this helps, but according to "the book" as you put it, you would still use the HTTP methods, you would just pass two arguments instead of one when you want to add two items. GET should be used to receive the resource, PUT to add to a resource, and POST to modify the resource. Once you decide which method is appropriate, then it becomes a matter of how many parameters you pass along, which for PUT, POST and DELETE can be limitless, if I understand correctly. GETs are not so limitless simply because they are putting your arguments and values on the address line which has a limit of how many characters can be there.
Any thoughts on this, or am I completely off base for those who know better than I?
Marnie
I don't know if this helps, but according to "the book" as you put it, you would still use the HTTP methods, you would just pass two arguments instead of one when you want to add two items. GET should be used to receive the resource, PUT to add to a resource, and POST to modify the resource. Once you decide which method is appropriate, then it becomes a matter of how many parameters you pass along, which for PUT, POST and DELETE can be limitless, if I understand correctly. GETs are not so limitless simply because they are putting your arguments and values on the address line which has a limit of how many characters can be there.
Any thoughts on this, or am I completely off base for those who know better than I?
Marnie
----- Original Message ----
From: Dan Glauser <danglauser@...>
To: sacjug@yahoogroups.com
Sent: Thursday, July 31, 2008 6:59:17 AM
Subject: [SacJUG Discussion] REST Question
From: Dan Glauser <danglauser@...>
To: sacjug@yahoogroups.com
Sent: Thursday, July 31, 2008 6:59:17 AM
Subject: [SacJUG Discussion] REST Question
Hello Fellow Sacjuggers,
I've been doing my own research into REST and I have a question I thought I'd throw out to the group.
A REST architecture provides a really simple way to GET, PUT, POST, DELETE a resource. But
let's say I need to accomplish a more complicated task in one step. Given an interface such as:
How would I add two items to an order in one step?
Also, would I handle something that is intrinsically verb based such as search?
I really like how simple REST is and how it makes use of the underlying protocol (HTTP), I just don't understand how you can elegantly design without additional verbs.
Are there any good online resources that talk about this? I have ordered "the book" but it hasn't arrived yet.
I'm looking forward to your talk Nick. Hopefully this discussion will help to peak some
interest.
Regards,
--
Dan Glauser