dido:public:ra:xapend:xapend.a_glossary:b:byzantine_generals_problem
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
dido:public:ra:xapend:xapend.a_glossary:b:byzantine_generals_problem [2021/07/24 14:21] nick |
dido:public:ra:xapend:xapend.a_glossary:b:byzantine_generals_problem [2021/10/04 09:51] (current) 66.249.69.248 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Byzantine Generals Problem ===== | ===== Byzantine Generals Problem ===== | ||
| - | [[dido:public:ra:xapend:xapend.a_glossary| Return to Glossary ]] | + | [[dido:public:ra:xapend:xapend.a_glossary:start| Return to Glossary ]] |
| **Byzantine Generals Problem** is when a reliable computer system must be able to cope with the failure of one or more of its components (i.e., [[dido:public:ra:xapend:xapend.a_glossary:b:byzantine_fault]].) A failed component may exhibit a type of behavior that is often overlooked -- namely, sending conflicting information to different parts of the system. The problem of coping with this type of failure is expressed abstractly as the Byzantine Generals Problem. (( | **Byzantine Generals Problem** is when a reliable computer system must be able to cope with the failure of one or more of its components (i.e., [[dido:public:ra:xapend:xapend.a_glossary:b:byzantine_fault]].) A failed component may exhibit a type of behavior that is often overlooked -- namely, sending conflicting information to different parts of the system. The problem of coping with this type of failure is expressed abstractly as the Byzantine Generals Problem. (( | ||
dido/public/ra/xapend/xapend.a_glossary/b/byzantine_generals_problem.1627150873.txt.gz · Last modified: 2021/07/24 14:21 by nick
