Sun Microsystems, Remote Method Invocation Specification, http://java.sun.com/products/jdk/rmi/, 1997.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....generating the graphics on the same site as the graphics hardware. J Orchestra operates at the Java bytecode level and rewrites the application code to replace local data exchange (function calls, data sharing through pointers) with remote communication (remote function calls through Java RMI [18], indirect pointers to mobile objects) The resulting application is guaranteed to have the same behavior as the original one (with a few, well identified exceptions) J Orchestra receives input from the user specifying the network locations of various hardware and software resources and the code ....

....directly, as in o1.a field , the code will have to change into o1.set a field(o1.get a field( 1) This rewrite will actually occur at the bytecode level. The above indirect reference techniques are not novel (e.g. see JavaParty [8] as well as the implementation of middleware like Java RMI [18]) The problem with indirect reference techniques, however, is that they do not work well when the remote object and the client objects are implemented in unmodifiable code. Typically, code is unmodifiable because it is native code i.e. code in platform specific binary form. For instance, the ....

[Article contains additional citation context not shown here]

Sun Microsystems, Remote Method Invocation Specification, http://java.sun.com/products/jdk/rmi/, 1997.

....already present on all the clients and servers. We do not perform any code migration and use coarse grained remote execution on the order of seconds. This granularity is appropriate for the class of applications being targeted. This is in contrast to other remote execution systems, like Java RMI [21], that perform finegrained remote execution on the order of microseconds. We assume that the individual remote calls that make up the remote execution are self contained and do not produce side effects. Since Chroma is meant to be used on mobile devices, we assume a highly variable resource ....

Sun Microsystems Inc. Remote Method Invocation Specification.

....generating the graphics on the same site as the graphics hardware. J Orchestra operates at the Java bytecode level and rewrites the application code to replace local data exchange (function calls, data sharing through pointers) with remote communication (remote function calls through Java RMI [18], indirect pointers to mobile objects) The resulting application is guaranteed to have the same behavior as the original one (with a few, well identified exceptions) J Orchestra receives input from the user specifying the network locations of various hardware and software resources and the code ....

....directly, as in o1.a field , the code will have to change into o1.set a field(o1.get a field( 1) This rewrite will actually occur at the bytecode level. The above indirect reference techniques are not novel (e.g. see JavaParty [8] as well as the implementation of middleware like Java RMI [18]) The problem with indirect reference techniques, however, is that they do not work well when the remote object and the client objects are implemented in unmodifiable code. Typically, code is unmodifiable because it is native code i.e. code in platform specific binary form. For instance, the ....

[Article contains additional citation context not shown here]

Sun Microsystems, Remote Method Invocation Specification, http://java.sun.com/products/jdk/rmi/, 1997.

....aspects, in that order. rersistence aspects are not considered here for scope and spae reasons. Examples are used to illustrate several aspects of rim, including some refinement laws and the constraints imposed on design methods. The current version of rim is specific to Java [4] and RMI [7], so that we use them throughout the paper. At the end we discuss the current status of this work and its limitations. Most tasks of Pim are just informally described and illustrated by examples. However, key tasks are formalized by semantic preserving refinement laws, which basically indicate ....

....RemoteException myBus ines s. addCustomer (customer) where the code inherited from the RMI class UnicastRemoteObject allows target adapters to be remotely accessed, and RemoteException is raised by RMI to notify communication or configuration problems during the call of a remote method [7]. As target adapters shall be used as remote objects, we must also have an interface with the same signature as the target adapter class: interface MyBusinessTargetRMIAdapter extends Remote throws Communicat ionExcept ion, Remot eExcept ion; where Remote is an RM interface used to ....

[Article contains additional citation context not shown here]

Sun Microsystems. Remote Method Invocation Specification, 1998.

....for individual programs. Perhaps, the functionality should be split, with the core part executed on the server, while the user interface is executed on the client. Communication between the two parts could be performed with standard distributed computing techniques (e.g. CORBA [9] or Java RMI [11] middleware) Perhaps, objects should migrate on demand, or according to an application specific pattern. Such circumstances give rise to application partitioning. Application partitioning is the task of breaking up the functionality of an application into distinct entities that can operate ....

Sun Microsystems, Remote Method Invocation Specification, http://java.sun.com/products/jdk/rmi/, 1997.

....interface defines a method called notify that will be called by the event generator whenever an event occurs. This framework of classes allows a distributed interaction because both event generators and event listeners are remote objects and their interaction is handled by means of RMI calls [15, 33]. Events in the Java Distributed Event Specification are objects implementing the RemoteEvent interface, so the modeling capability for events is good. However, the filtering capability is rather limited. Event no42 tifications have an event id of type long, and a listener can select events ....

Sun Microsystems, Inc., Mountain View CA, U.S.A. Remote Method Invocation Specification, 1997.

....hardware, instead of passing all drawing commands over the network. J Orchestra operates at the Java bytecode level and rewrites the application code to replace local data exchange (function calls, data sharing through pointers) with remote communication (remote function calls through Java RMI [18], indirect pointers to mobile objects) The resulting application is guaranteed to have the same behavior as the original one. J Orchestra receives input from the user specifying the network locations of various hardware and software resources and the code using them directly. A separate profiling ....

....directly, like in o1.a field , the code will have to change into o1.set a field(o1.get a field( 1) This rewrite will actually occur at the bytecode level. The above indirect reference techniques are not novel (e.g. see JavaParty [8] as well as the implementation of middleware like Java RMI [18]) The problem with indirect reference techniques, however, is that they do not work well when the remote object and the client objects are implemented in unmodifiable code. Typically, 3 code is unmodifiable because it is in a platform specific or native form the implementation of Java system ....

[Article contains additional citation context not shown here]

Sun Microsystems, Remote Method Invocation Specification, http://java.sun.com/products/jdk/rmi/, 1997.

....which allows a programmer to invoke methods on specified remote objects. 2 The appearance of such a remote invocation is similar to a local (residing in the same address space) invocation. RMI uses object serialization mechanism to handle the necessary marshaling unmarshaling details [Sun96a, Sun96b, Hor96, Orf97]. RMI allows an easy implementation of client server applications, which are prominent in business domains. While RMI is easy to use, one drawback is that, it invokes the remote methods synchronously, i.e. when the client invokes the method, it must wait for the server to respond with the result ....

....new, more comprehensive system, thus making it incompatible with currently existing RMI technology. 2. 2 RMI and ARMI The RPC model, however, does not translate well into distributed object systems, where communication between program level objects residing in different address spaces is needed [Sun96b]. In order to match the semantics of object invocation, distributed systems require RMI. In such systems, a local surrogate (stub) object manages the invocation on a remote object [Sun96b] The principles of RMI are similar to those of RPC. However, the presence of inheritance, polymorphism and ....

[Article contains additional citation context not shown here]

Sun Microsystems, Inc. Java (TM) Remote Method Invocation Specification, 1996.

....editing session in which the root is the controller, the current token policy is return to controller . Mary is the user presented with the edit window with the text area disabled (gray) as she does not have the edit token: The implementation is based on Java Remote Method Invocation (RMI) see [Sun Microsystems 1997], which provides a semi transparent means for clients to access remote objects. The use of the Common Object Request Broker Architecture (CORBA) see [Object Management Group 1998] was considered as an alternative to RMI during design, but Java s built in support for RMI provided an easier ....

Sun Microsystems. Remote Method Invocation Specification. On-line. Available: http://www.javasoft.com/products/jdk/1.1/docs/guide/rmi/spec/rmiTOC.doc.html (11 September 1998).

....At application level the reconfiguration capability of the system allows the incorporation of new capabilities into applications directly at run time. The native programming model of HARNESS is distributed, Object Oriented components cooperating through Remote Method Invocation (RMI) [4]. However, the modular, Object Oriented nature of the HARNESS system allows on demand mix and match of components or complete applications adopting programming models that are different from its native one. This process is supported by means of compatibility suites [5] that can be plugged into the ....

Sun Mycrosystems, Remote Method Invocation Specification, available on line at http://java.sun.com/products/jdk/1.2/docs/g uide/rmi/index.html, July 1998.

....support for distributed computing commonly provide two level addressing. This provides the ability to use local and remote references interchangeably. References that arrive on a site are automatically converted to the local form if they refer to local entities. Typical examples include Java RMI [Sun Microsystems 1997], CORBA [Otte et al. 1996] and the Ericsson OTP (Open Telecom Platform) Armstrong et al. 1996; Wikstrom 1994] Two level addressing can be extended to provide weak logic variables (see also Section 2.1.4) It suffices to add an unknown state to variables: 1) threads block when the variable ....

Sun Microsystems. 1997. The Remote Method Invocation Specification. Available at http://www.javasoft.com.

.... robust multithreaded architecture; it allows users to develop additional services both in a passive, library like flavor and in an active thread enabled flavor; it provided us an Object Oriented mechanism to require services from remote computational resources (Java Remote Method Invocation [5]) it provided us a generic methodology to transfer data over the network in a consistent format (Java Object Serialization [6] it allowed us to provide to users the definition of interfaces to be implemented by plug ins implementing the basic services; it allowed us to tune the ....

Sun Mycrosystems, Remote Method Invocation Specification, http://java.sun.com/products/ jdk/1.2/docs/guide/rmi/index.html, July 1998.

....How can we achieve this In the current state of the art, developing a distributed application with these properties requires specialist knowledge beyond that needed to develop an application on a single machine. For example, a new client server application can be written with Java RMI [23, 24]. An existing application can be connected with another through a CORBA implementation (e.g. Orbix) 26] Yet in both cases the tools are unsatisfactory. For example, reorganizing the distribution structure requires rewriting the application. Furthermore, with each major problem that is ....

....in Distributed Oz obey a lightweight object migration protocol that preserves centralized object semantics and allows for precise prediction of network behavior. Existing systems with mobile objects do not use such an algorithm. They move the objects by creating a chain of forwarding references [24, 15, 5]. This chain is short circuited when a message is sent or after a given time delay. This gives good average case number of network hops when moving an object, but very bad worst case number of hops. A design principle of Distributed Oz is for third party dependencies to always eventually ....

[Article contains additional citation context not shown here]

Sun Microsystems. The Remote Method Invocation Specification. Sun Microsystems, Mountain View, Calif., 1997. Available at http://www.javasoft.com.

.... using a robust multithreaded architecture; users can develop additional services both in a passive, library like flavor and in an active thread enabled flavor; an Object Oriented mechanism is available to request services from remote computational resources (Java Remote Method Invocation [4]) a generic methodology is available to transfer data over the network in a consistent format (Java Object Serialization [5] users are provided the definition of interfaces to be implemented by plug ins implementing the basic services; the trade off between portability and efficiency ....

Sun Mycrosystems, Remote Method Invocation Specification, available on line at http://java.sun.com/products/jdk/1.2/docs/guide/rmi/ index.html, July 1998.

.... a robust multithreaded architecture; it allows users to develop additional services both in a passive, library like flavor and in an active threadenabled flavor; it provided us an Object Oriented mechanism to require services from remote computational resources (Java Remote Method Invocation [5]) it provided us a generic methodology to transfer data over the network in a consistent format (Java Object Serialization [6] it allowed us to provide to users the definition of interfaces to be implemented by plug ins implementing the basic services; it allowed us to tune the ....

Sun Mycrosystems, Remote Method Invocation Specification, available on line at http://java.sun.com/products/jdk/1.2/docs/guide/rmi/index. html, July 1998.

.... multithreaded architecture; it allows users to develop additional services both in a passive, library like flavor and in an active thread like or process like flavor; it provided us a generic RPC mechanism to require services from remote computational resources (Java Remote Method Invocation [4]) it provided us a generic methodology to transfer data over the network in a consistent format (Java Object Serialization [5] it allowed us to provide to users the definition of interfaces to be implemented by plug ins implementing the basic services; it provided us a generic ....

Sun Mycrosystems, Remote Method Invocation Specification, available on line at http://java.sun.com/products/jdk/1.2/docs/guide/rmi/index.html, July 1998.

No context found.

Sun Microsystems, Remote Method Invocation Specification, http://java.sun.com/products/jdk/rmi/, 1997.

No context found.

Sun Microsystems, Remote Method Invocation Specification.

No context found.

Sun Microsystems, Remote Method Invocation Specification.

No context found.

Sun Microsystems, Remote Method Invocation Specification, http://java.sun.com/products/jdk/rmi/, 1997.

No context found.

Sun Microsystems, Remote Method Invocation Specification, http://java.sun.com/products/jdk/rmi/, 1997.

No context found.

S. Microsystems. The remote method invocation specification, dec 2002. Available from http://java.sun.com.

No context found.

Sun Microsystems, Remote Method Invocation Specification, http://java.sun.com/products/jdk/rmi/, 1997.

No context found.

Sun Microsystems, Remote Method Invocation Specification, 1998

No context found.

Sun Microsystems, Remote Method Invocation Specification. 1997. http://java.sun.com/products/jdk/1.1/docs/ guide/rmi/spec/rmiTOC.doc.html.

First 50 documents

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