I had a computer arch prof who used to refer to self-tests in digital logic as the ability for circuits and chips to test for their own sanity. As the implementaiton gets smaller, the ability to test for sanity could get more difficult. For example, some of the experimenetal nano-media are prone to faults and its only in the massive redundncy, that they are usefull. I wonder about the ability of an attacker in the future to manipulate the fault level of digitial logic/memory, or the self-tests of digital logic. Could the attacker able to introduce this fault manipulate a higher order operation like a math op and therefore gain access to some variation of Shamir's attack.
Many people ask about relational fidelity and MySQL. However, my experience out in the developer world is that a lot of developers want to put most of the business rules of a domain model in the application code. For example, stored procedures, triggers, check constraints all seem to be disfavoured over implementing these things in application code, object models or frameworks. This type of focus seems to be the most important relational fidelity concern. Do you feel that is better to put the busines rules in the application code? If so for what reasons.
Slashdot Mirror
I had a computer arch prof who used to refer to self-tests in digital logic as the ability for circuits and chips to test for their own sanity. As the implementaiton gets smaller, the ability to test for sanity could get more difficult. For example, some of the experimenetal nano-media are prone to faults and its only in the massive redundncy, that they are usefull. I wonder about the ability of an attacker in the future to manipulate the fault level of digitial logic/memory, or the self-tests of digital logic. Could the attacker able to introduce this fault manipulate a higher order operation like a math op and therefore gain access to some variation of Shamir's attack.
Many people ask about relational fidelity and MySQL. However, my experience out in the developer world is that a lot of developers want to put most of the business rules of a domain model in the application code. For example, stored procedures, triggers, check constraints all seem to be disfavoured over implementing these things in application code, object models or frameworks. This type of focus seems to be the most important relational fidelity concern. Do you feel that is better to put the busines rules in the application code? If so for what reasons.