title: GET or PUT to reboot a remote resource?
body: <p>I am struggling (in some sense) to determine which HTTP method is more appropriate for rebooting a remote resource: GET or PUT? </p>
  
  <p>On one hand, it seems more semantic to call <code>http://tools.serviceprovider.net/canopies/d34db33fc4f3?reboot=true</code> because one might want to GET a representation of a freshly rebooted canopy. </p>
  
  <p>On the other hand, a reboot is not 'safe' (nor is it necessarily idempotent, but then a canopy or modem is not just a row in a database) so it might seem more semantic to PUT the canopy into a state of rebooting, then have the server return a 202 to indicate that the reboot was initiated and is processing.</p>
  
  <p>I have been reading up on HTTP/1.1, REST, HATEOAS, and other related concepts over the last week, so I am still putting the pieces together. Could a more seasoned developer please weigh in and confirm or dispel my hunch?</p>