Comments for Ecommerce on Sinatra: A Shopping Cart Story

[phinjensen]

Comments for https://www.endpointdev.com/blog/2011/03/ecommerce-sinatra-shopping-cart/ By Steph Skardal

To enter a comment:

1. Log in to GitHub
2. Leave a comment on this issue.

[phinjensen]

original author: Clint Pachl
date: 2011-03-04T23:16:48-05:00

Because Sinatra's beautiful DSL makes REST so easy, you could update your routes:

app.post '/cart/add' app.post '/cart/update' app.get '/cart/remove/:product_id'

to a more RESTful version:

app.post '/cart' app.put '/cart/:product_id' app.delete '/cart/:product_id'

Then enable the Sinatra :method_override option to automatically detect the HTTP verb sent in forms (e.g. _method="put"). Then remember to include _method as a hidden variable in PUT and DELETE forms.

Here's a RESTful resource table: http://guides.rubyonrails.org/routing.html#crud-verbs-and-actions

Great article; very professionally done.

[phinjensen]

original author: Steph Skardal
date: 2011-03-07T09:50:11-05:00

Thanks for the comments - I'll look into cleaning up these RESTful routes.

[phinjensen]

original author: joselo
date: 2011-06-29T01:09:18-04:00

talking about shopping carts, I wondering if should I duplicate or save the product in other table just for the reason that the user can have an inventary of their orders and if I modify the product that the client bought it will be an inconsistence. Because the cliente will see a differente product, do you know what I mean :), wich could be a good solution without make an asociation directly with the product model. I'm not sure but a duplicate table.. that sucks :-(

Any ideas, thanks!

[phinjensen]

original author: Ronny Ager-Wick
date: 2011-10-18T12:14:56-04:00

joselo, if you don't want to store a duplicate of your product model on the order lines, you can:

• extend the product model with a version number
• whenever a product it modified, don't overwrite it - instead store it again using the same id, but a higher version number
• any process requesting a product without a specific version number gets served the latest version - for example when viewing a product in the shop
• when adding a product to an order (or probably more accurately, when the order has been confirmed/paid), store the product id and the version number
• when displaying an order, you know the version number for each product and can thus display the "old version" of the product