Agree with all this. But you can't code for every possibility in existence, you still have to pick and choose, according to the feasibility criterion ;-)
On 13/05/2014 09:36, Bert Verhees wrote: > On 13-05-14 10:12, Thomas Beale wrote: >> this bit is true. Do you have such pathological data? > In an open system, or a SOA-environment, or when selling it, one does > not always have control over data being offered to a system. > > Software-system lives in an ecosystem of software. > > That is why nesting needs to be controlled, I have seen systems which, > because of a bug dive into a recursive loop, and spit out data and > feed it to another system. If it is an automated process, and it does > in a few separated threads, your OpenEHR kernel can crash, and if it > runs in a operating system with a notorious reputation regarding > process-management, even that can crash. > > I have seen server systems which did not even allow to login, because > there was no processor-time left to handle the login-process. > > Thinking about precautions regarding malformed-data-entry in software > is a good thing.
