you are correct - always use a database for your products - but for maintaining persistant information (ie: what items are in their cart etc) I use xml - its a lot easier to deal with - before that I would rely on session variables (ick) to maintain their information for their session.
~Eric On Thursday, July 4, 2002, at 08:28 AM, Jenda Krynicky wrote: > From: Eric Plowe <[EMAIL PROTECTED]> > >> I have a suggested method for handling your shopping cart - I can't >> provide any code examples off hand (I am a asp/.net/vb/c++ programmer >> - waits for the flames :D ) here's what I do when I construct shopping >> carts > > I am not the person who started the thread! > > Well while we have something like shopping cart in the project I am > working on, it's not in the parts I work at. I don't like the way > it's done, but that's not my bussines. > >> Use xml! it's easy to work with and pretty fast. > > I would expect a real database to be quicker. Especialy since we > connect to the database anyway. I do not know, but I find XML a > little strange for state data. It's good for transfering data between > systems and such stuff, but for things that tend to change very often > it doesn't seem too good. IMHO of course. > > Jenda > =========== [EMAIL PROTECTED] == http://Jenda.Krynicky.cz ========== > There is a reason for living. There must be. I've seen it somewhere. > It's just that in the mess on my table ... and in my brain > I can't find it. > --- me > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
