Re: Using REST service created with IWS

[Booth Martin <booth@xxxxxxxxxxxx>]

Walk me through this.  The temperature conversion example included with 
IWS...  The address is http://an.iSeries.com/coop/ I want to say F2C and 
90, meaning I want the api to convert 90 degrees Fahrenheit to 
Celsius.   What should that look like?


On 1/14/2019 4:16 PM, Tim Fathers wrote:
> While I agree the definition of REST can be pretty flexible and there are no hard and fast rules, I think it is a fairly well established rule of thumb that the URL should generally identify the resource, not the query parameters. The body (which I think you mean by "standard input") is where the payload should go, and should not be used on on a GET request in any case.
>
> In some APIs the resource is not a "thing" but a function, in which case it is considered ok to pass query parameters to it in the URL for a GET or in the body for a POST. The example of this from my favourite REST book "The RESTful Webservices Cookbook" is a distance calculator. So /calc_distance?from=wiesbaden&to=frankfurt is ok because "distance" is not a thing but a function.
>
> Tim.