Sun Microsystems. Java Remote Method Invocation Specication. Sun Microsystems, October 1998.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....eld in its parameters and obtains the address assigned by the proxy. Once the BrowserServer object is initialized and prepared to service requests from the playground, it binds a remote reference to itself to the address assigned by the proxy; this binding is stored in an RMI name server [14]. The proxy remembers what address it assigned to each applet tag and provides this address to the playground in a similar fashion. That is, the proxy loads applets into the playground by sending to the playground an HTML page with identical ContactAddress param tags to what it forwarded to ....

Sun Microsystems, Inc. Java Remote Method Invocation Speci cation, 1997.

....programming languages, computational power, and network bandwidth. Conventionally, programming in the face of such heterogeneity has depended either on application specic messaging protocols or on higher level remote procedure call systems such as RPC [4] DCOM [6] CORBA [28] or Java RMI [33]. RPC style systems have proven successful in a wide variety of programs and problem domains. They have some important limitations, however, and their wide acceptance does not necessarily imply that there is no alternative approach to addressing heterogeneity. In this paper we consider the ....

Sun Microsystems Inc. Java Remote Method Invocation Specication. Mountain View, CA, 2001. Avaialble at http://java.sun.com/j2se/1.4/docs/guide/rmi/spec/rmiTOC.html.

....also have other non functional requirements such as concurrency and persistence, which make their implementation a complex task. To support implementation, we have seen the development of language and tools for distribution. For instance, Java [5] has a distributed object model provided by RMI [8], which supports the implementation of distributed object collaborations in the language itself without the need for low level protocols. In addition, RMI also provides a compiler tool for automatic generation of components involved in development of distributed applications. However, language ....

....or distribution, does not entail the need to redevelop the whole system. This tutorial presents software architectures for distributed applications, introduces a design pattern for re ning these architectures, and details the implementation of this pattern using the following technologies: RMI [8], JINI [9] and CORBA [6] The ideas in this tutorial are based on previous research [2, 10] where structuring guidelines for distributed applications were presented. However, the main contribution of this work is to represent these guidelines abstractly as a design pattern and show how to ....

[Article contains additional citation context not shown here]

Sun Microsystems. Java Remote Method Invocation Speci cation, 1.50 edition, October 1998.

....an entity to cooperate with others in its vicinity, it rst needs to discover other entities as it moves into a new location. This problem of service discovery has recently been explored in the context of distributed systems and elsewhere. State of the art systems such as Jini[1] Salutation [20], Universal Plug and Play (UPnP) 16] as well as IETF s draft Service Location Protocol[18, 23] provide for networked entities to advertise their functionality. Within these newly emerged distributed systems, our evaluation [6] shows that Jini provides a more exible and robust service discovery ....

Sun Microsystems, 901 San Antonio Road, Palo Alto, CA 94303, USA. Java Remote Method Invocation Speci cation, revision 1.5, jdk 1.2 edition, Oct. 1998.

....execute on the nodes of a workstation cluster. The distributed nature of the environment is mostly hidden from the application by providing a shared object space across all participating virtual machines. To make objects accessible from other nodes, Java s remote method invocation (RMI) is used [7]. Instead of asking the programmer to insert many verbose RMI commands manually into his multi threaded Java application to port is from a single workstation to a cluster, JavaParty allows him to declare classes to be remote. JavaParty then generates all the necessary RMI commands automatically ....

Sun Microsystems Inc., Mountain View, CA. Java Remote Method Invocation Speci cation, October 1998. ftp://ftp.javasoft.com/docs/jdk1.2/rmi-spec-JDK1.2.pdf.

....of values is not allowed, e.g. unwrapping the Long argument and narrow the resulting long value to the formal parameter int is not possible 4 . The reverse case does not require any casts, therefore it is allowed (e.g. assigning a String argument to an Object formal parameter) Compared to RMI [RMI96], dynamic RMCs don t require a stub skeleton compiler. The disadvantage is that as there is no strong typing method calls may fail at run time (e.g. method is not found) However, generating strongly typed client stubs from a class that uses dynamic RMCs should be easy: a compiler would parse ....

Sun Microsystems Inc. Java Remote Method Invocation Specication, 1.1 edition, November 1996. Draft.

....a signature speci c Op object, so the generated Java code must provide support for dynamic lookup of operations. This support is provided by access methods used to retrieve the appropriate operation object. 5. 6 Remote Class Loading The dynamic class loading described in the Java RMI speci cation [42] allows for class les to be loaded from either the local CLASSPATH or from a prede ned URL. The JR run time system requires only that necessary class les for the program be accessible through the CLASSPATH at the originating host (where the program is initially executed) When a remote object is ....

Sun Microsystems, Palo Alto, CA. Java Remote Method Invocation Specication, 1997.

....that supports and encourages the production of reliable distributed services [1] and nally, the services themselves, that can be made part of a federated Jini system and which o er functionality to any other member of the federation. The infrastructure is composed of the Java RMI protocol [6], which enables objects to communicate through remote method invocations, and the lookup service [1] which de nes how services may become part of a Jini systems and clients retrieve services by their types and attributes. Java RMI and the lookup service are based on the concept of proxy, which is ....

Sun Microsystems. Java Remote Method Invocation Specication, Rev. 1.50. Sun Microsystems, Inc., Mountain View, California, October 1998.

....none of them has been developed modifying the RMI system inner code, as it is done by our toolkit, in order to obtain a ne grained control over mechanisms such as remote reference updating and object tracking. 2 MobileRMI The main goals of the Java distributed object model are the following [7]: 1. Support seamless remote invocation on objects in di erent address spaces. 2. Integrate the distributed object model into the Java language in a natural way while retaining most of the Java s object semantics. 3. Make di erences between the distributed object model and the local Java object ....

Sun Microsystems. Java Remote Method Invocation Specication, October 1998.

....lookup service. This proxy then handles communication with the server. This mechanism allows devices and services to be dynamically added and removed from the system. Also, proxy and server can choose their own protocol for communicating with each other. The underlying Java and RMI infrastructure [12] provides advantages of security, ease of code shipping, and platform independence, but also incurs the drawbacks of restriction to one language, and the potential performance penalties and unpredictability of a virtual machine. 7 Conclusions Loadable smart proxies can be used to encapsulate ....

Sun Microsystems. Java remote method invocation specication, October 1998.

....protocol and delivery scheme between the Ronin Agent and Agent Deputy. For example, DeputyArthur, a concrete Agent Deputy implementation, is implemented to communicate with the owner Ronin Agent through the Distributed Event model [12] which is based on the Remote Method Invocation infrastructure [11]. Another concrete Agent Deputy implementation, DeputyArjun, is implemented to communicate with the owner Ronin Agent through the generic network socket model, and is designed to handle the customized store and forward [2] message delivery scheme. Agent Deputies can be easily designed and ....

Sun Microsystems, 901 San Antonio Road, Palo Alto, CA 94303, USA. Java Remote Method Invocation Specication, revision 1.5, jdk 1.2 edition, October 1998.

.... programming community has investigated numerous communication paradigms for distributed environments, such as message passing libraries (e.g. mpi or pvm) communication channels (e.g. csp or calculus) remote procedure call (rpc) and its object oriented variant, remote method invocation [45, 46]. Nexus [19, 35] is a distributed programming paradigm, available as a library, that provides the essence of a distributed object system and has inspired the model of communication used in sofar. Nexus is the communication layer used in the Globus projects (www.globus.org) the basis of the ....

Sun MicroSystems. Java Remote Method Invocation Specication, November 1996.

....However, as the application still depends on the network to get the information needed to its execution, the model is not robust enough to deal with communication failures, nor capable to operate disconnected from the network. Java also support control mobility through the library Java RMI [10]. Recently, mobile agents have been considered as an alternative to the construction of Internet distributed systems. A mobile agent is a program that can roam through the machines of a network, carrying the state of its execution. Telescript [12] was the rst language to support the ....

Sun Microsystems. Java Remote Method Invocation Specication, Oct. 1998. 12 Valente et al.

....resource is used can no longer be taken locally, but must involve a collaboration with the di erent locations participating in the computation. Distributed reference counting may be used to implement distributed garbage collection; a variant of this technique is in particular used in Java and RMI [24, 37]. Even though distributed reference counting is not able to deal with distributed cycles, it has been a popular implementation technique of distributed garbage collection because it is simple to implement and can be nicely integrated with sequential garbage collectors [3, 24, 29, 39] More ....

....participating to the computation. In order to reduce the burden on individual sites, we present a hierarchical organisation of the reference listing algorithm by which we are able to give a bound to the size of send tables. JAVA Remote Method Invocation comes with a distributed garbage collector [37]. It extends Birrel s reference listing technique with a new approach to fault tolerance, where remote pointers are leased for a period of time. Sites having pointer copies must regularly renew their lease. Our approach can be extended without problem to reference listing so that send tables ....

Sun MicroSystems. Java Remote Method Invocation Specication, November 1996.

No context found.

Sun Microsystems. Java Remote Method Invocation Specication. Sun Microsystems, October 1998.

No context found.

Sun Microsystems. Java Remote Method Invocation speci cation. Technical report, Sun Microsystems, 1997.

No context found.

SUN Microsystems. Java Remote Method Invocation Speci cation, 1998.

No context found.

S. Microsystems. Java remote method invocation specication, 1998.

No context found.

Sun Microsystems, Palo Alto, CA. Java Remote Method Invocation Speci cation, 1997.

No context found.

S. Microsystems. Java remote method invocation specication, 1998.

No context found.

Sun Microsystems. Java Remote Method Invocation Specication, December 1999. http://java.sun.com/products/jdk/1.3/docs/guide/rmi/.

No context found.

S. Microsystems. Java remote method invocation specication, 1998.

No context found.

S. Microsystems. Java remote method invocation specication, 1998.

No context found.

Sun Microsystems Inc., Mountain View, CA. `Java Remote Method Invocation Speci cation'. 1996. BIBLIOGRAPHY 85

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