title: Side effects on other resources
body: <p>This is a theory / best practices question regarding RESTful and HATEOAS design...</p>
  
  <p>Given the resources:</p>
  
  <blockquote>
    <p>/myresources/  (a collection of our resource objects)</p>
  </blockquote>
  
  <p>and</p>
  
  <blockquote>
    <p>/transactions/ (a collection of historical transactions that have occurred in the system)</p>
  </blockquote>
  
  <p>Is it a valid practice for:</p>
  
  <blockquote>
    <p>POST /myresources/</p>
  </blockquote>
  
  <p>to not only create a new resource at /myresources/ but also a new resource at /transactions/?</p>
  
  <p>In other words, can a POST (or any verb) to one URL effect resources at both that URL and others?  Is there another approach?  Obviously we could use two POSTs, but that requires us to trust the user to maintain valid state across multi-resource modifications.</p>