A better idea might be to map carts to sessions, and then sessions to customers.
Each session has a cart. Each cart may belong to more than one session. A customer can identify with more than one session, although each session can only identify with up to one customer. This way, the customer can put stuff in their cart at home, go to work, add some more stuff, and then come home, and have everything in their cart. The customer has two active sessions because the browser at work and the browser at home don't share cookies. Plus, your logs will have a more realistic picture of what's really going on, since each session maps to exactly one browser. On Jan 25, 9:54 pm, Matt Woolnough <[email protected]> wrote: > Thanks guys for your input. > > I found a couple of threads on stackoverflow on similar questions: > > http://stackoverflow.com/questions/1969711/best-way-to-place-temporar...http://stackoverflow.com/questions/964476/store-in-session-data-vs-st... > > Although it seems there will be a performance penalty for this type of > arrangement, I think I'll attempt to implement something like what > Jonathan suggests. Hopefully the decision doesn't turn out to be a > bad one... Oh well it's all just a learning experience eh? > > cheers again > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
