title: REST Shopping cart
body: <p>Can a shopping cart be implemented using REST architecture constraints? </p>
  
  <p>I would like to focus my question with respect to session state. In a typical MVC application implementing a shopping cart, it most likely, session object will be managed in session, shopping cart as a list of products.</p>
  
  <p>How would this same shopping cart be managed in if the application had followed REST architecture. One of the REST constraints is state management is  responsibility of clients. </p>
  
  <p>Should a shopping cart and it's progress be managed by client? Any examples? Any disadvantages of managing state in client with respect to a simple shopping cart or any other enterprise applications?</p>