Implementing Fault-Tolerant Distributed Objects
dc.contributor.author | Birman, Kenneth P. | en_US |
dc.contributor.author | Joseph, Thomas A. | en_US |
dc.contributor.author | Raeuchle, Thomas | en_US |
dc.contributor.author | El Abbadi, Amr | en_US |
dc.date.accessioned | 2007-04-23T16:50:32Z | |
dc.date.available | 2007-04-23T16:50:32Z | |
dc.date.issued | 1984-03 | en_US |
dc.description.abstract | This paper describes a technique for implementing $k$-resilient objects - distributed objects that remain available, and whose operations are guaranteed to progress to completion, despite up to $k$ site failures. The implementation is derived from the object specification automatically, and does not require any information beyond what would be required for a non-resilient, non-distributed implementation. It is therefore unnecessary for an appplications programmer to have knowledge of the complex protocols normally employed to implement fault-tolerant objects. Our technique is used in ISIS, a system being developed at Cornell to support resilient objects. | en_US |
dc.format.extent | 1159107 bytes | |
dc.format.extent | 463357 bytes | |
dc.format.mimetype | application/pdf | |
dc.format.mimetype | application/postscript | |
dc.identifier.citation | http://techreports.library.cornell.edu:8081/Dienst/UI/1.0/Display/cul.cs/TR84-594 | en_US |
dc.identifier.uri | https://hdl.handle.net/1813/6434 | |
dc.language.iso | en_US | en_US |
dc.publisher | Cornell University | en_US |
dc.subject | computer science | en_US |
dc.subject | technical report | en_US |
dc.title | Implementing Fault-Tolerant Distributed Objects | en_US |
dc.type | technical report | en_US |