title: REST - complex applications
body: <p>I'm struggling to apply RESTful principles to a new web application I'm working on.  In particular, it's the idea that to be RESTful, each HTTP request should carry enough information by itself for its recipient to process it to be in complete harmony with the stateless nature of HTTP.</p>
  
  <p>The application allows users to search for medications.  The search accepts filters as input, for example, return discontinued medicines, include complimentary therapy etc..etc.  In total there are around 30 filters that can be applied.   </p>
  
  <p>Additionally, patient details can be entered including the patients age, gender, current medications etc.</p>
  
  <p>To be Restful, should all this information be included with every request?  This seems to place a huge overhead on the network.  Also, wouldn't the restrictions on URL length, at least for GET, make this unfeasible?</p>