| Schlichting, R. D. and Thomas, V. T. (1995) Programming language support for writing fault-tolerant distributed software. IEEE Trans. Comput., 44, 203--212. |
....in those applications where processes are autonomous entities, that need to cooperate with some atomicity guarantees. However, this model is not suitable for transactional systems where servers are passive entities that are only activated when clients request services. Some programming languages [18, 19] have incorporated group communication primitives and features for replication, recovery and failure noti cation. Although, no facilities for transaction processing are available. A di erent integrative approach has been the use of group communication as a building block to implement database ....
R. Schlichting and V. T. Thomas. Programming Language Support for Writing Fault-Tolerant Distributed Soft. ACM Trans. on Comp.
....management, and communication. An illustration of this is given in Figure 2 where fault tolerant code is spread throughout the dataManager written in a programming language such as SR. Figure 2. Fault tolerant distributed software written in programming language such as SR [1] Adapted from [20]) SF s Distributed Computing Environment (DCE) 17] treats aspects in a monolithic manner residing in object management layer. Further, objectoriented based systems like Amoeba [23, 16] and Choice [3] treat aspects monolithically residing in object management as well. 4. An Aspect Oriented ....
Richard, S., Thomas, V., Programming Language Support for writing Fault-Tolerant Distributed Software, IEEE transactions on Computers, Vol. 44, No. 2, pp.203-212, February 1995.
....to remove the right to bind the variable, for example, when passing the variable to a less trusted site. Partially bound variables. Garbage collection. The failure model. The Oz algorithm is conservatively extended with a basic failure model based on the concepts of watchers and handlers [11, 25]. Full treatment of the model is beyond the scope of this paper. We briefly summarize the main ideas. The occurrence of a temporary or permanent failure causes any attempted operation on a variable to block for the duration of the failure. The detection of a failure may invoke watchers and ....
Richard D. Schlichting and Vicraj T. Thomas. Programming language support for writing fault-tolerant distributed software. IEEE Transactions on Computers, 44(2):203--212, February 1995.
....used in supporting faulttolerant computing. The first approach provides programming languages that are targeted at developing fault tolerant systems. Typical examples of this approach are the Ada 95 [1] the Fault Tolerant Concurrent C [2] and the fault tolerant version of the SR language [3]. The second approach provides a faulttolerant computing toolkit or a model that can be used together with general programming languages and standard operating systems. Typical examples of this approach are the ISIS toolkit [4] the ARGUS system [5] the location based replication paradigm [6] ....
R. D. Schlichting and V. T. Thomas. Programming language support for writing fault-tolerant distributed software. IEEE Transactions on Computer, 44:203-- 212, 1995.
No context found.
Schlichting, R. D. and Thomas, V. T. (1995) Programming language support for writing fault-tolerant distributed software. IEEE Trans. Comput., 44, 203--212.
No context found.
Richard D. Schlichting and Vicraj T. Thomas. Programming language support for writing fault-tolerant distributed software. IEEE Transactions on Computers, 44(2):203--212, February 1995.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC