Timeline for Which HTTP verb should I use to trigger an action in a REST web service?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 3, 2014 at 21:26 | comment | added | Benjamin Hodgson | I agree. Things like configuration and caching are meant to be transparent to the client. Maybe you should give us a more concrete description of a situation in which your endpoint would be called. | |
| Nov 2, 2014 at 3:50 | comment | added | user22815 | I still agree. Invoking SIGHUP on a local process makes sense, since the computer should trust someone logged in locally who has access to that signal. But for a stateless, Internet-accessible protocol? Perhaps the web service should automatically reload as necessary via polling or file monitoring. This call should be completely unnecessary. | |
| Nov 2, 2014 at 2:52 | comment | added | Renato Dinhani | Look at my edit. "reload" is not a command that returns data. It refers to the REST web service itself. In general terms, my question refers about triggering actions in a REST web service. Other example can be: email_queue/stop_sending_emails. I am justing giving a command to something using a RESTful interface. | |
| Nov 2, 2014 at 2:25 | history | answered | Thomas Stringer | CC BY-SA 3.0 |