Ask HN: Using REST design for complex function calls?
2 comments
There's nothing about REST that requires you do use GETs for everything, quite the opposite in fact (read up on how the Rails REST API is designed for some inspiration).
Then again, unless you want to make a given function/input combination into a resource, you might be better of with a less RESTy approach.
Then again, unless you want to make a given function/input combination into a resource, you might be better of with a less RESTy approach.
Right, it wasn't that I thought you had to use GETs for everything, but that, being these are calls that change nothing on the server, GET was appropriate.
Because the functions require complex - potentially, arbitrarily large - inputs, it's too difficult to pass them in via GETs.
Is there discussion or articles somewhere about using REST for computational APIs rather than for resource-based APIs?