| C. Neusius. Synchronising actions. In Proceedings of ECOOP'91, LNCS 512, pages 118--132, Geneva, Switzerland, July 1991. Springer-Verlag. 595, 597 |
....independent COOP language the type implemented by a class is independent from the functionality part of the class definition. Essentially, the functionality code of the class is encapsulated from the synchronisation code of the class. Examples of implementation independent languages are [6,14,24,26]. Some of these proposals encapsulate the concurrency issues into a separate class in order to facilitate re use of the concurrency part. Naturally, a language may be implementation independent with respect to one notion of types, while not being implementation independent with respect to a ....
.... internal CUBL [27] GUARDS Yes KEYS Yes No No ACT [17] ACCEPT SETS Yes No No No No Types f ROSETTE [30] ACCEPT SETS Yes No No No No Types f DEMETER [20] GUARDS Yes KEYS Yes LOC R LOC R Types f MAUDE [25] PATTERNS Yes No Yes No No Types f MAUDE [18] PATTERNS Yes No Yes LOC R LOC R Types f [ 26] GUARDS SETS Yes Yes Yes LOC R LOC R Types f [ 6 ] GUARDS Yes Yes Yes LOC R LOC R Types f BALLOON [5] GUARDS Yes KEYS Yes LOC R LOC R Types f GUIDE [12] GUARDS Yes KEYS Yes No No Types f [ 13] GUARDS Yes No Yes LOC R No DOOJI [29] GUARDS SETS Yes KEYS LOC R No No Types f [ 15] GUARDS No No ....
C. Neusius. Synchronising actions. In Proceedings of ECOOP'91, LNCS 512, pages 118--132, Geneva, Switzerland, July 1991. Springer-Verlag. 595, 597
....though usually some form of inter object concurrency is supported. Other active object models do support internal concurrency. For example, an object may have a thread of control which receives and schedules requests; and when a request may start execution, another thread is created to service it [17]. Most mechanisms have inherent limitations which makes then suitable for only one object model, and less suitable, or even totally unsuitable, for others. For example, Caromel s mechanism [9] provides good support for scheduling requests; however it provides no facilities to manage internal ....
Christian Neusius. Synchronising Actions. In Pierre America, editor, ECOOP '91, pages 118--132, Geneva, Switzerland, July 1991. Springer-Verlag. Available as Volume 512 of Lecture Notes in Computer Science.
....variables, instead permitting them to access instance variables. We have shown that this access is usually either unsafe or at the expense of a reduction of the potential for concurreny within objects. Aside from Esp, at least two other mechanisms Mediators [GC86] and Synchronising Actions (SA) Neu91] propose a complete segregation of synchronisation code and variables from sequential code and variables. However, in papers on these mechanisms, the authors take it as read that modularity is desirable and do not mention that without it there would be problems with synchronisation code ....
Christian Neusius. Synchronising Actions. In Pierre America, editor, ECOOP '91, pages 118--132, Geneva, Switzerland, July 1991. Springer-Verlag. Available as Volume 512 of Lecture Notes in Computer Science.
....policies offer additional benefits, including facilitating the optimisation of synchronisation code. Analysis of the problems with the use of inheritance in COOPLs. A common belief is that there is a conflict between synchronisation and inheritance that can hinder the reuse of code [TS89] KL89] Neu91] GW91] Tho94] Loh93] BBI ] Mes93] BFS93] Mat93] Cou94] Ber94] We show that this perception of the conflict is incorrect; rather, the problem is rooted in the conflicting interaction of two different uses of inheritance. We survey the conflict in a variety of inheritance mechanisms ....
....synchronisation mechanisms. The literature is quite sparse on synchronisation paradigms especially ones that are comparable to Sos. However, we did come across two such paradigms; we discuss them in Sections 6.1.1 and 6.1.2. 6.1. 1 Synchronising Actions The Synchronising Actions (SA) paradigm [Neu91] contains concepts that correspond approximately to the core concepts of Sos. Thus, it makes sense to compare these two paradigms on the basis of these concepts. The first concept of the Sos paradigm is that of events and the code (actions) executed at them. SA is also event based. Code ....
[Article contains additional citation context not shown here]
Christian Neusius. Synchronising Actions. In Pierre America, editor, ECOOP '91, pages 118--132, Geneva, Switzerland, July 1991. Springer-Verlag. Published as volume 512 of the Lecture Notes in Computer Science series.
....it is necessary to provide concurrency control mechanisms that avoid unlegal interferences. Appears in Proc IEEE International Workshop on Future Trends in Distributed Computing Systems. 1993. Research supported by the Swiss FNS under contract number 5003 034344. Many authors [8] 2] [10] have discussed the design of object concurrency controls that preserve internal state invariants, e.g. a bank account balance has always to be positive. Preserving this intra object coherency goes through scheduling object invocations (scheduling in the small) Another form of coherency, which we ....
....necessary to separate the concurrency control code from operation implementations. Adding an operation to a subclass would lead to a concurrency control modification. Such modification would not have any effect on the operations if the concurrency control is designed in an independent manner [8] [10]. Moreover, to ease the reuse of the concurrency control itself, it is important to dispatch it into several parts. It is thus possible to refine parts of the concurrency control without modifying the whole. 2.3 Heterogeneity Transaction concurrency control has been studied for over twenty years ....
C. Neusius -"Synchronising Action" - Proceedings of the European Conference on Object Oriented Computing - June 1991.
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