It makes little sense to ask a Rock to "PUT" or "GET" anything either given that its an inert object not actually capable of interaction.
I think Pete's point on the name not being important is interesting in theory, but in reality the names are extremely important as they will be assumed to indicate what can be done, and at a business level it would make more sense to "order lunch" in a restaurant than it would be to "POST" my order to them. On 06/06/07, Mark Baker <[EMAIL PROTECTED]> wrote:
Agreed, with one minor nit... On 6/6/07, Peter Lacey <[EMAIL PROTECTED]<placey%40wanderingbarque.com>> wrote: > It goes like this: REST the style mandates a uniform interface. It > does not say what that interface should be. It could, for instance, be > read, write, update, order_lunch. order_lunch isn't uniform. It makes no sense to, for example, ask a rock to order lunch for you. Mark.
