>Yes, this is not on witango, but I experience this failure of web objects at
>the apple store - I can't imagine a scenario where witango would do this:
>
>I placed an order and it isn't shipped immediately. Back ordered. So I check
>on the order status daily (okay, more than once a day), and found that the
>session variables time out at maybe 10 minutes or so. Twice I hit the "order
>history" link right near the end of that period, I got neither a "timed out"
>nor my orders, but a dump (14MB) with a link to every order placed at the
>apple store over the last few weeks. It tends to crash my browser, but it
>nevertheless is a type of failure that shouldn't be possible. It looks like
>the user variables don't all time out at the same moment, allowing the
>search to go forward, but the specific user id to default to 'all' rather
>than my own id.
>
>Bad woa
As a previous user of Web Objects, I would have to say this is a common
problem with the product. I was using the $30k+ version at the time.
Apple said that the upgrade (v3.5?) would fix the problem but we bailed
on it. I have since experienced the problem at several WO sites including
the Apple Store.
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
