Cart
[Home] [By Thread] [By Date] [Recent Entries]
At 10:45 AM -0600 1/6/04, Hunsberger, Peter wrote: >How do you balance between tracking flow with stateless systems (as in >shopping cart check out) and caching (performance optimization)? If you >don't use Cookies you've got to write some unique state identifier into >the response/request cycle. Preferably not in the URL so as a parameter >to be passed back on the POST. Since this identifier must be unique for >each user you've now destroyed the ability to cache the page generically >and instead must generate it uniquely for each user. I'd argue the only >rational choice is cookies (preferably non-persistent)... I'm not sure I quite understand you here. Perhaps you could give a more concrete example? Most shopping cart apps I'm aware of are very dynamic and customize heavily per user and per page. Otherwise how could you show the user what's in their basket? So I don't think you'd want to cache this at all, with or without cookies, but maybe I'm missing something? -- Elliotte Rusty Harold elharo@m... Effective XML (Addison-Wesley, 2003) http://www.cafeconleche.org/books/effectivexml http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA
|
