Re: Standard Queue status

[Ted Dennison<dennison@telepath.com>]

In article <9u6e1d$903$1@nh.pace.co.uk>, Marin David Condic says...
>requirements as built. I can't possibly get 101 elements into it and have
>that be the camel that breaks its straw back. I'd have to rebuild the
>software tweaking that size upwards - presumably I'd be smart enough to test
>the *new* worst case. For sure I know I've got a different set of bits now
>and the verification of the original bits is null and void.

Stuff like that can happen in our system quite easily. For example, a user who
knows just enough about the system to be dangerous could theoriticaly decide
that the navigational model is behaving too sluggishly for them, and go into our
configuration file and bump its iteration rate up to 30Hz where it doesn't even
have time to complete before the next iteration. Then they will start to get
overrun messages all over the place. Our answer to this is: "Don't do that". The
configuration stuff is there for diagnotic purposes, not for casual twiddling. 

---
T.E.D.    homepage   - http://www.telepath.com/dennison/Ted/TED.html

No trees were killed in the sending of this message. 
However a large number of electrons were terribly inconvenienced.