Hi Matt,

From your notes, I realized how much time you must have into extending all
the order manipulation commands.  It would seem like the only current course
of action is to fully load test your solution to understand if it will stand
up under your predicted loads before trying to steer the boat a different
direction.

Just out of curiousity, I never saw it mentioned but I assumed you were
building this on WC 5.6 BE.  Is that correct?

geo
--
George Niece
J2EE Solutions Architect
eGlobal Solutions
office:760-742-3820
direct:760-807-8823
<matt.senter@brunswickboatgroup.com> wrote in message
news:1011013331.1115323468734.JavaMail.wassrvr@ltsgwas007.sby.ibm.com...
> No problem. Any time the user touches their cart (i.e. add an item, update
an item, begin the checkout process,) the clock resets. There is no warning.
If the user is at the cart screen and steps away for lunch, performing any
action on the cart when they return (supposing lunch is longer than 15
minutes of course,) will throw an exception that converts the cart into a
requisition list and takes the user to the req list page. That allows them
to quickly add all the items back to the cart if they need to continue with
the order, only now they're at the back of the line again so-to-speak.

[ Post a follow-up to this message ]