Alright, I have a ReST API which exposes an artifact whose state is "stopped". To start it in a ReSTful way, naturally I PATCH the artifact with a new state, "running". But what if I now want to *restart* it in a ReSTful way?
-
actually, wait, PATCHing "running" is cheating. You've got a RESTful Zeno's paradox where you go from stopped to running with no time in between; where's the "starting" state? What starts immediately? And in what sense can it then restart? How does restarting alter its state?
For the sake of argument, say the HTTP request doesn't return until the thing is started
