Andrew Black, Norman Hutchinson, Eric Jul, Henry Levy, and Larry Carter, "Distribution and Abstract Types in Emerald", in IEEE Trans. Softw. Eng., 13(1):65-76, 1987.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....closely resembling the JOrchestra approach are object based DSMs, like Orca [3] The Orca system has a dedicated language and run time system, but also has similarities to J Orchestra in its treatment of data at the object level, and its use of static analysis. Mobile object systems, like Emerald [4][10] have similarities with J Orchestra. Many of the J Orchestra ideas on implementing mobile objects and choosing appropriate semantics for method invocations (synchronous object migration) have originated with Emerald. The Doorastha system [6] represents another piece of work closely related to ....

Andrew Black, Norman Hutchinson, Eric Jul, Henry Levy, and Larry Carter, "Distribution and Abstract Types in Emerald", in IEEE Trans. Softw. Eng., 13(1):65-76, 1987.

....closely resembling the JOrchestra approach are object based DSMs, like Orca [3] The Orca system has a dedicated language and run time system, but also has similarities to J Orchestra in its treatment of data at the object level, and its use of static analysis. Mobile object systems, like Emerald [4][10] have similarities with J Orchestra. Many of the J Orchestra ideas on implementing mobile objects and choosing appropriate semantics for method invocations (synchronous object migration) have originated with Emerald. The Doorastha system [6] represents another piece of work closely related to ....

Andrew Black, Norman Hutchinson, Eric Jul, Henry Levy, and Larry Carter, "Distribution and Abstract Types in Emerald", in IEEE Trans. Softw. Eng., 13(1):65-76, 1987.

....to mention a few, and they allow rogrammers to easily make an object accessed by a remote hostthrou( a network. The rogrammers only have to define the interface of the object in an interface definition lang u ge. Another exam le is to up a distribuJ rogramming langu age like Emerald[3]. Su ch a langu age rovides langu age constru cts for creating objects on remote hosts, migrating them to another host, and so on. However, these rogramming tools and environments are mainly for develo ing new distribu ted software from scratch; they are not for ada ting legacy ....

Andrew Black, Norman Hutchinson, Eric Jul, Henry Levy, and Larry Carter, Distribution and Abstract Types in Emerald, In IEEE Transactions on Software Engineering, Vol.SE-13, No.1, IEEE, pp.65--76, 1987.

....Good techniques for placement, replication, and mobility have been developed and appear in the distributed systems literature. These include placement and data consistency techniques from Distributed Shared Memory systems (e.g. Orca [2] object mobility techniques (e.g. from the Emerald system [3]) etc. Additionally, with a judicious combination of static analysis and execution profiling, distribution decisions can be more educated than in past systems. In the spectrum of technologies aimed at facilitating distributed computing, automatic partitioning is among the most ambitious, because ....

Andrew Black, Norman Hutchinson, Eric Jul, Henry Levy, and Larry Carter, "Distribution and Abstract Types in Emerald", in IEEE Trans. Softw. Eng., 13(1):65-76, 1987.

....is effected using invocation of methods on meta objects in the meta object hierarchy through reflectors. Reflectors act as entry points to metaobjects. Significant work has been done in developing metaobject protocols for languages [10] 13] and in the theoretical aspects of reflection. Emerald [4] has shown the importance of type conformity in distributed systems. Even industrial projects are paying increasing attention to flexible interaction between objects and facilities for dynamic modifications. One of the most important is CORBA by OMG [15] 19] CORBA is a software platform for ....

A. Black, et al, Distribution and Abstract Types in Emerald, IEEE Trans. Software Eng., 13(1), Jan. 1987, pp. 65-76.

....is extracted automatically from the Smalltalk library. An interface hierarchy is a logical organization of the interfaces of each class in a library. The interface hierarchy is a partial order that factors out shared interfaces, using the notion of conformance (or subtyping) for interfaces [Cardelli84, CM89, BHJLC86]. An algorithm for computing the interface hierarchy of a Smalltalk class library is described. When applied to the Smalltalk 80 Collection classes, the program produces a descriptive picture of the sharing of messages among classes. Even for a language like Smalltalk, which supports only single ....

....methods occur surprisingly often in the Smalltalk collection library and are a significant source of confusion in trying to understand collection behavior. 2. 2 The Protocol Hierarchy The protocol hierarchy arises from the partial order of protocols by the conformance, or subtype, relationship [Cardelli84, CM89, BHJLC86]. Interface B conforms to interface A if every object that satisfies B also satisfies A. This means that the set of objects satisfying B is a subset of the set satisfying A. However, the interface B, viewed as a set of operations, is typically larger (more specific) than the interface A. For the ....

A. Black, N. Hutchinson, E. Jul, H. Levy and L. Carter. "Distribution and abstract types in Emerald." IEEE Transactions on Software Engineering SE--13:1, 1987.

....resembling the J Orchestra approach are object based DSMs, like Orca [3] The Orca system has a dedicated language and run time system, but also has similarities to J Orchestra in its treatment of data at the object level, and its use of static analysis. Mobile object systems, like Emerald [4][10] have similarities with J Orchestra. Many of the J Orchestra ideas on implementing mobile objects and choosing appropriate semantics for method invocations (synchronous object migration) have originated with Emerald. The Doorastha system [6] represents another piece of work closely related to ....

Andrew Black, Norman Hutchinson, Eric Jul, Henry Levy, and Larry Carter, "Distribution and Abstract Types in Emerald", in IEEE Trans. Softw. Eng., 13(1):65-76, 1987.

....may have different implementations. For example, we may want to have different source code implementations of a image convolution computation based on whether it is run on a multiprocessor, multicomputer, networks of workstations, or vector machine. This is known as implementation families [3] and it would fit in nicely with our model a set of callbacks would be provided for each implementation. Implementation families would likely contain highly tuned and optimized implementations. One difficulty with multiple implementations is the issue of compatibility. It may not make sense ....

A. Black, N. Hutchinson, E. Jul, and H. Levy, "Distribution and Abstract Types in Emerald," University of Washington, TR 85-08-05, August, 1985.

....architecture which is currently being implemented. Section 7 covers some related works. Finally, section 8 concludes this paper. 2 Motivations 2. 1 Implementation hiding These days, object oriented concept has proved to be the solution for distributed computing with its message sending mechanism[5, 10]. And, in many distributed OOPLs[5, 10] a class is required to be shown as two separate modules one is the interface of a class which can be accessed by all users regardless of their sites, and the other is the implementation of a class, used only for implementation of the class. So ....

....implemented. Section 7 covers some related works. Finally, section 8 concludes this paper. 2 Motivations 2. 1 Implementation hiding These days, object oriented concept has proved to be the solution for distributed computing with its message sending mechanism[5, 10] And, in many distributed OOPLs[5, 10], a class is required to be shown as two separate modules one is the interface of a class which can be accessed by all users regardless of their sites, and the other is the implementation of a class, used only for implementation of the class. So Account Deposit Loan moneyManager Figure ....

[Article contains additional citation context not shown here]

A. Black, N. Hutchinson, E. Jul, H. Levy, and L. Carter. "Distribution and Abstract Types in Emerald". ACM Computing Surveys, 19(2):105-- 190, June 1987.

....(in Argus) and Ejects (in Eden) are usually large units, such as servers, objects in Guide are usually small (like files in traditional systems) and may be combined into larger units. This resulted in the decision to make Guide objects passive, in contrast with both Argus and Eden. In Emerald [4], a successor project to Eden, static type checking is introduced, and objects may be active or passive. The main features of the system include a single object model (unlike Eden and Argus) support for abstract types and an explicit notion of object location and mobility. The type conformity ....

....number of processes; and b) separate objects from execution structures, i.e. define passive objects executed by independently defined processes. We did not find strong arguments in favor of either solution. Both have been adopted in existing object based systems (e.g. active objects in Emerald [4]; passive objects in Clouds [10] Amoeba [12] and SOS [16] The two solutions are dual: both can offer the same functionality to the user, but in different ways. The choice is mostly influenced by considerations of efficiency and adequacy to the hardware and to the applications. Our system is ....

Black, A.P., Hutchinson, N., Jul, E., Levy, H., and Carter, L., "Distribution and Abstract Types in Emerald," IEEE Trans. on Software Engineering, vol. SE-13, no. 1, pp. 65-76, 1987.

....load. Status: A prototype implementation is constructed. Research is going on to implement the features of object mobility and distributed garbage collection. Contact: Andrew Black, Department of Computer Science, FR 35, University of Washington, Seattle, Washington 98195. References: 169] [170] 2.22 GAFFES Main Goal GAFFES (Global, Active and Flexible File Environment Study) is a study of a globally distributed file system designed to share information in a world wide network consisting of more than a million workstations. GAFFES, designed at the University of California in Berkeley, ....

A. Black, N. Hutchinson, E. Jul, H. Levy, and L. Carter, "Distribution and Abstract Types in Emerald", IEEE Transactions on Software Engineering, SE--13(1):65--76, January 1987.

....to execute computations spanning a number of physical nodes on a network, and to move objects from one node to another. Few synchronization mechanisms have been proposed for object oriented systems, the main reason being that few such systems support concurrency and shared objects. In Emerald [1], the only synchronization tool provided is a monitor construct allowing the encapsulation of data and methods with exclusive access. Trellis Owl [12] proposes a similar tool: locks and wait queues. In Hybrid [13] delay queues allow scheduling activities in the same way as condition variables ....

A.P. Black, N. Hutchinson, E. Jul, H. Levy, L. Carter, Distribution and abstract types in Emerald, IEEE Trans. on Software Engineering, vol SE-12, dec. 1986.

No context found.

Black, A. P., Hutchinson, N., Jul, E., Levy, H. M. and Carter, L. " Distribution and Abstract Types in Emerald" . IEEE Trans. on Software Eng. SE-13, 1 (January 1987), pp.65-76.

No context found.

Black, A. P., Hutchinson, N., Jul, E., Levy, H. M. and Carter, L. "Distribution and Abstract Types in Emerald". IEEE Trans. on Software Eng. SE-13, 1 (January 1987), pp.65-76.

No context found.

A. Black, N. Hutchinson, E. Jul, H. Levy and L. Carter, `Distribution and abstract types in Emerald', IEEE Trans. Software Engineering, SE-13, (l), 65-76 (1987).

No context found.

A. Black, N. Hutchinson, E. Jul, H. Levy and L. Carter, `Distribution and abstract types in Emerald', IEEE Trans. Software Engineering, SE-13, (l), 65--76 (1987).

....machines and moves them in response to changes in local load. Thus, a user can create a distributed application which moves around an interconnection using otherwise idle workstations. Thus, run time systems are freed from the job of tracking mobile activations. Some languages, such as Emerald [4], implement remote activations through data object mobility. ARCADE s data units are easily replicated across machine boundaries. This decreases the need for messages between active objects in order to invoke an Emerald like method. Emerald allows replications of only immutable data objects. ....

Black, A., Hutchinson, N., Jul, E. Levy, H. and Carter, L., "Distribution and Abstract Types in Emerald," IEEE Transactions on Software Engineering, Volume SE-13, No. 1, January 1987.

No context found.

Andrew Black, Norman Hutchinson, Eric Jul, Henry Levy, and Larry Carter, "Distribution and Abstract Types in Emerald", in IEEE Trans. Softw. Eng., 13(1):65-76, 1987.

No context found.

Black, A., Hutchinson, N., Jul, E., Levy, H., and Carter, L.: Distribution and Abstract Types in Emerald. IEEE Trans. on Software Engineering, Vol. SE-13, no. 1, January 1987, 65--76.

No context found.

A. Black, N. Hutchinson, E. Jul, H. Levy,and L. Carter,"Distribution and Abstract Types in Emerald," IEEE Transactions on SoftwareEngineering,vol. SE-13, no. 1, pp. 65-76, January 1987.

No context found.

Andrew Black, Norman Hutchinson, Eric Jul, Henry Levy, and Larry Carter, "Distribution and Abstract Types in Emerald", in IEEE Trans. Softw. Eng., 13(1):65-76, 1987.

No context found.

A. Black, N. Hutchinson, E. Jul, H. Levy and L. Carter "Distribution and Abstract Types in Emerald", IEEE Transactions on Software Engineering, SE-13, 1, pp. 65-76, 1987.

No context found.

Andrew P. Black, Norman Hutchinson, Eric Jul, Henry Levy, and Larry Carter, "Distribution and Abstract Types in Emerald," IEEE Transactions on Software Engineering, December 1986.

No context found.

A. Black, et al., "Distribution and Abstract Types in Emerald", IEEE Transactions on Software Engineering, January 1987, pp. 65-76.

No context found.

A. Black, N. Hutchinson, E. Jul, H. Levy, and L. Carter, "Distribution and Abstract Types in Emerald," IEEE Transactions on Software Engineering, vol. SE-13, no. 1, pp. 65-76, January, 1987.

First 50 documents  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