Gosling J., Joy B. and Steele G., "The Java^TM Language Specification ", Addison-Wesley, 1996 Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Aspects of Synchronisation - Holmes, Noble, Potter (1998) (2 citations) (Correct)
....so there is a single entry and exit point for all messages. The inner ring is a sliding scale behaviour, so we have different entry and exit points for increase operations and decrease operations. 5. Current Status and Future Work We have developed an initial implementation in Java TM [Gos96] to experiment with the implementation of different synchronisation behaviours and the required semantics of those behaviours. Each synchronisation ring is implemented as a single object with entry, exit and rollback points implemented as methods. A synchronised object consists of one or more ....
Gosling J., Joy B. and Steele G., "The Java^TM Language Specification ", Addison-Wesley, 1996
Synchronisation Rings - Composable Synchronisation for.. - Holmes (1999) (Correct)
....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 ....
....are invoked by external threads of control there must be some way to create these threads of control. This may be done by directly using native operating systems 17 features (such as using system calls in C [Str91] by encapsulating the notion of thread in a special class (as is done in Java [Gos96] and other object oriented concurrency libraries) or through language constructs that cause new activities to be created (such as the thread methods of Mitchell s TAO system [Mit95] see Section 2.5.1) In passive object systems concurrent activities could be executing in the same or in ....
[Article contains additional citation context not shown here]
Gosling J., Joy B. and Steele G., "The Java^TM Language Specification", Addison-Wesley, ISBN 0-201-663451-1, 1996
Concurrency, Synchronisation and Objects - Holmes (1999) (Correct)
....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 ....
....are invoked by external threads of control there must be some way to create these threads of control. This may be done by directly using native operating systems 17 features (such as using system calls in C [Str91] by encapsulating the notion of thread in a special class (as is done in Java [Gos96] and other object oriented concurrency libraries) or through language constructs that cause new activities to be created (such as the thread methods of Mitchell s TAO system [Mit95] see Section 2.5.1) In passive object systems concurrent activities could be executing in the same or in ....
[Article contains additional citation context not shown here]
Gosling J., Joy B. and Steele G., "The Java^TM Language Specification", Addison-Wesley, ISBN 0-201-663451-1, 1996
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 ....
....per object is simply not a practical on existing hardware systems, thus the OOCP systems tended to move towards hybrid approaches where passive objects are contained within active ones. On the other hand object languages, such as Smalltalk [Gol83] C [Str91] with library support) and Java TM [Gos96], took the view that objects were passive and inanimate, only coming alive when activated by a thread of control executing one of its methods. Such languages contain only passive objects but allow the creation and destruction of new threads of control. The early languages did not concern ....
[Article contains additional citation context not shown here]
Gosling J., Joy B. and Steele G., "The Java^TM Language Specification", Addison-Wesley, ISBN 0201 -663451-1, 1996
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