Hi

"I know your guys are going to hate the "getCustomer" verb encoded in URI, and I definitely agree that this, together with the query style (?id=abc), are not very RESTful semantics. However, we can look into this problem from two aspects:"

It's RESTful to have /getcustomer embedded in the URI as long as this is an HTTP GET. It's just that 'GET' here is part of the HTTP-the-application protocol, so there's just no need to give a hint to a server through '*get*customer' that a customer state needs to be retrieved. HTTP GET is a hint.

Cheers, Sergey


Reply via email to