On 5/16/07, Nathan Harmston <[EMAIL PROTECTED]> wrote:
...
> So far I am thinking of storing the whole shopping cart as a
> dictionary in session where it is simply
>
> { product_id:amount },Assuming low site concurrrency, no. I don't know why you'd want to take that approach as opposed to having a cart model, but if it floats your boat, go for it. If you have high concurrency, just realize that session storage and retrieval involves deserialization of the state bag out of the DB, which is an additional overhead compared to general models, whose data marshalling is performed by the (highly optimized) DB server and client code. Your session table could also become a hot spot in the DB since you'll be writing a larg-ish single row rather than many smaller rows. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
