| George Niece 2005-05-05, 6:04 pm |
| Hi again Matt,
Is the user notified in anyway about the impending timeout? If so, how are
you notifying the user that their current cart is going to time out? Is the
timeout 15 minutes from adding the first or last item to the cart (or
updates to the cart)?
Sorry to be so nosy, but I figured your requirements might need to be a bit
more exposed to understand what you were trying to accomplish and how to
best suggest a path.
geo
--
George Niece
J2EE Solutions Architect
eGlobal Solutions
office:760-742-3820
direct:760-807-8823
<matt.senter@brunswickboatgroup.com> wrote in message
news:1555814026.1115304850788.JavaMail.wassrvr@ltsgwas007.sby.ibm.com...
> Heh, no it will have quite a load if and when it is ever fully released.
The carts have to be emptied because they work with live inventory. What you
see in your cart is pulled off the virtual shelf in the warehouse, meaning
no one else can buy it while you have it. It stays in your cart until you
either check out, remove it, empty the cart, or you hit the 15-minute time
limit. It's a B2B site, so you probably won't be seeing it on any TV
specials. I guess I should have prefaced this whole thing with "I'm having
to create a bunch of workarounds to actually get past built-in Commerce
functionality because Commerce did not fit the business but IBM sold it to
management anyway." I wish I could go into more detail (this is just the tip
of the iceberg really,) but I've fought for over a year now to change
peoples' minds here, and it has proven impossible. They aren't interested in
good scalable solutions...just "Git 'r dun."
|