Mitchell S. E., "TAO - A Model for the Integration of Concurrency and Synchronisation in Object Oriented Programming", Ph.D. dissertation, Dept. of Computer Science, York University, UK, 1995  Home/Search Document Details and Download
Summary Related Articles Check |
This paper is cited in the following contexts:
Synchronisation Rings - Composable Synchronisation for.. - Holmes (1999) (Correct)
....message acceptance until the appropriate conditions are met. In some systems the programmer must explicitly write the code for controlling message acceptance, by defining a so called body routine [Ame87] whilst in others the programmer need only specify the synchronisation conditions. Mitchell [Mit95], however, defines an active object as any object that encapsulates a thread of control even if that thread does not perform message acceptance a situation which is more generally regarded as a passive object model. Lhr [Lh92] also associates active with the use of any encapsulated thread. ....
....and which are writers) to ensure interference does not occur. The existence of multiple active threads of control within a single object is known as intra object concurrency. 2.2.3 Passive Objects In the most basic sense passive objects are simply not active ones. In passive object systems [Baq95, Gol83, Gos96, McH94, Mit95, Str91], objects do not have internal message processing threads, rather their methods are invoked directly by external threads of control. These threads of control represent the activities of the system and these activities interact and communicate by manipulating shared objects. Of course not all ....
[Article contains additional citation context not shown here]
Mitchell S. E., "TAO - A Model for the Integration of Concurrency and Synchronisation in Object-Oriented Programming", Ph.D. Dissertation, Department of Computer Science, York University, UK, 1995
Concurrency, Synchronisation and Objects - Holmes (1999) (Correct)
....message acceptance until the appropriate conditions are met. In some systems the programmer must explicitly write the code for controlling message acceptance, by defining a so called body routine [Ame87] whilst in others the programmer need only specify the synchronisation conditions. Mitchell [Mit95], however, defines an active object as any object that encapsulates a thread of control even if that thread does not perform message acceptance a situation which is more generally regarded as a passive object model. Lhr [Lh92] also associates active with the use of any encapsulated thread. ....
....and which are writers) to ensure interference does not occur. The existence of multiple active threads of control within a single object is known as intra object concurrency. 2.2.3 Passive Objects In the most basic sense passive objects are simply not active ones. In passive object systems [Baq95, Gol83, Gos96, McH94, Mit95, Str91], objects do not have internal message processing threads, rather their methods are invoked directly by external threads of control. These threads of control represent the activities of the system and these activities interact and communicate by manipulating shared objects. Of course not all ....
[Article contains additional citation context not shown here]
Mitchell S. E., "TAO - A Model for the Integration of Concurrency and Synchronisation in Object-Oriented Programming", Ph.D. Dissertation, Department of Computer Science, York University, UK, 1995
Effective Synchronisation of Concurrent Objects: Laying.. - Holmes, Noble, Potter (1998) (Correct)
....active objects then there must also be passive objects objects without their own thread of control, but whose methods are executed in threads of control that originate from other objects. Concurrent object oriented languages exist which support purely active models [Agh87, Lie87] purely passive [Baq95, Gos96, McH94, Mit95, Str91] or a hybrid combination [Act92, Ame87, Car90a, Jal93, Kar92, Loh92, Mey96, Nie92, Yok87] 2 The pure active models were based on the notion of ACTORS [Agh86] but having a process (or thread) per object is simply not a practical on existing hardware systems, thus the OOCP systems tended to move ....
....concurrent interactions, so problems with reuse began to surface. Eventually these reuse issues were studied in more detail and the term inheritance anomaly was coined to describe them [Mat90] Since then nearly all new language proposals have been promoted as solving the inheritance anomaly [Baq95, Ber94, Fer95, Fro92, Lop94, Mat93, McH94, Mit95]; but while they might have avoided one or more of the problems categorised by Matsuoka, they didn t really address all of the issues of reuse. In some cases the quest for reuse seems to have been abandoned altogether [Lop97] While the academic world developed the 98 (and more) concurrent ....
[Article contains additional citation context not shown here]
Mitchell S. E., "TAO - A Model for the Integration of Concurrency and Synchronisation in Object Oriented Programming", Ph.D. Dissertation, Department of Computer Science, York University, UK, 1995
Developing a Real-time Metaobject Protocol - Mitchell, Burns, Wellings (1996) Self-citation (Mitchell) (Correct)
....differing numbers of servers or replication strategies. 3 Using Reflection within a Real Time Framework 3.1 The Concurrency Model Before discussing reflection and metaobject protocols it is helpful to describe the model of concurrency envisaged. The chosen model has been heavily influenced by TAO [Mitchell 1995, Mitchell Wellings 1996] and thus adopts the concept of tasks encapsulated within objects to form active objects. Each active object can posses multiple internal tasks which are created when the encapsulating object is created and executed in conformance with the system schedule. Tasks interact ....
....into it. instance variables in synchronised objects or through calls to private synchronised methods within the object. The precise details of the final synchronisation scheme are not relevant to this paper, however, details of a potentially suitable (but non reflective) scheme can be found in [Mitchell 1995]. The active object approach allows for the dynamic creation and destruction of tasks via their encapsulating object and for concurrency control and task monitoring via the relevant metaobject. Later sections of this paper will discuss the mechanisms for controlling object creations to maintain ....
S. E. Mitchell, TAO - A Model for the Integration of Concurrency and Synchronisation in Object-Oriented Programming, University of York, UK, 1995 (Report number: YCST-95-009).
Aspects of Synchronisation - Holmes, Noble, Potter (1998) (2 citations) (Correct)
No context found.
Mitchell S. E., "TAO - A Model for the Integration of Concurrency and Synchronisation in Object Oriented Programming", Ph.D. dissertation, Dept. of Computer Science, York University, UK, 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