Failure semantics
![]() | Template:Wikify is deprecated. Please use a more specific cleanup template as listed in the documentation. |
![]() | This article contains no links to other Wikipedia articles. (December 2008) |
Failure Semantics:
Example (service): � A crash error is when nothing happens. � An omission error is when is when one or more responses fails. A crash is a special case of omission when all ropiness fails. � A timing error is when is when one or more responses do not arrive in time. An omission error is a timing error when a response has infinite timing error. � An arbitrary error is any error, i.e. a wrong value or a timing error. � When a client uses a server it can cope with different type errors from the server. � If it can manage a crash at the server it is said to assume the server to have crash failure semantics � If it can manage an service omission it is said to assume the server to have omission failure semantics � Failure Semantics are the type of errors that we expect to appear. � Should another type of error appear it will lead to a service failure since we can not manage it.
This article has not been added to any content categories. Please help out by adding categories to it so that it can be listed with similar articles. (December 2008) |