B. Liskov. Distributed Programming in Argus. In Communications of ACM, 31(3):300312. March 1988.  Home/Search   Document Not in Database   Summary   ACM   TOC   Related Articles   Check

....to this particular agent. The communication model is based on that proposed by the Aglets Workbench. Basically, aglets communicate via asynchronous messages that return future replies . These are based on futures and promises developed by Barbara Liskov as part of the Argus research project [Lisk88]. In addition, we propose that all kinds of messages supported by a particular agent class from which agents are created should be registered in one or more ACSs. Agents can also communicate directly by calling public methods on other agents. However, the following requirements should be ....

B. Liskov. Distributed Programming in Argus. In Communications of ACM, 31(3):300312. March 1988.

....OS level, because data objects are always invoked locally, can be recycled by some local mechanism, and don t require any extra functionality for the purpose of remote invocations. Many systems support this distinction, either by implementing two different object abstractions (for example, Argus [16] or by inheritance from different system classes (for example, the CORBA compliant systems) Having two different object abstractions breaks the uniformity of the object model, and implies that server objects be handled differently from data objects. Defining server characteristics by ....

....we are using GOOP RT, a very simple system developed for the purpose of testing these ideas. GOOP RT is an object server that provides a remote invocation service on C objects executing on the same address space; it uses the IK Remote Procedure Call library [19] and runs on top of UNIX. 16 5 Related Work This work is integrated in a much larger project that targets the engineering of distributed objectoriented applications [10] Therefore, it shares the same conceptual ideas and the same implementation strategy of synchronization patterns [18] It also shares the basic class ....

Barbara Liskov. Distributed Programming in Argus. Communications of the ACM, pages 300-- 312, March 1988.

.... As the volume of data managed by real time applications increases, there is incentive to apply database system concepts in the development of real time systems [Son88, Koo90, AGM88, KSS90] The transaction paradigm, in particular, seems to be applicable to real time systems [GR91, DLW90, SZ88, Lis88, Koo90, SL90] However, the timing requirements of real time systems appear to preclude the use of transaction management techniques at least in their current form. Among the obstacles to using transaction management technology in real time systems are: ffl High variance in access time for a ....

B. Liskov. Distributed programming in argus. Communications of the ACM, 31:300--312, March 1988.

....OS level, because data objects are always invoked locally, can be recycled by some local mechanism, and don t require any extra functionality for the purpose of remote invocations. Many systems support this distinction, either by implementing two different object abstractions (for example, Argus [18] or by inheritance from different system classes (for example, the CORBA compliant systems) Having two different object abstractions breaks the uniformity of the object model, and implies that server objects be handled differently from data objects. Defining server characteristics by ....

....the object oriented analysis and design methodologies. Most of the methodologies presented so far are based on graphs of objects or classes that describe object interactions at the design phase. Examples are the Booch method [5] OMT [27] Objectory [11] and many others. GOOP class graphs can be 18 seen as design graphs, but we use them directly as program text. Design methodologies usually don t consider any optimizations of the applications. The adaptive parameter passing scheme proposed in this paper handles optimization at a very high level of abstraction, so that it could be ....

Barbara Liskov. Distributed Programming in Argus. Communications of the ACM, pages 300-- 312, March 1988.

.... consequences do we have to expect while using the original BirliX object model ffl Are there security requirements forbidding a dynamical adaptation 5 Related ork There are several object oriented systems (e.g. Argus, Emerald) delivering their own language to define operating system objects ([8], 9] Here the adaptation of types for programming language objects to types for system supported objects is embedded in the compiler of the special language. So a large part of the compiler depends on the underlying system and is not easy adaptable to other object models. There are many ....

Barbara Liskov, "Distributed Programming in Argus ", Communications of the ACM, Vol. 31, No. 3, March 1988.

....A group may contain elementary objects executing in different contexts. However, an elementary object cannot be contained in multiple groups, so there is no sharing. SOS is not intended to address the problems of sharing rapidly changing data. PROFIT facets are similar to Argus objects [Liskov 88] If PROFIT objects and processes were not distinct, but instead every object was also a process, the result would closely match Argus guardians. Argus s lightweight processes are analogous to PROFIT s threads. A guardian consists of three parts, an interface (a set of handlers) internal ....

Barbara Liskov. Distributed Programming in Argus. Communications of the ACM 31(3):300-312, March, 1988.

Documents 51 to 100  Previous 50  Next 50

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