Topic
Dynamic Invocation Interface
About: Dynamic Invocation Interface is a research topic. Over the lifetime, 238 publications have been published within this topic receiving 6052 citations.
Papers published on a yearly basis
Papers
Journal Article•
TL;DR: A distributed object model for the Javarul System that retains as much of the semantics of the Java object model as possible, and only includes differences where they make sense for distributed objects is shown.
Abstract: We show a distributed object model for the Javarul System [Arnold & Gosling 1996; Gosling et al. 19961 (hereafter referred to simply as \"Java\") that retains as much of the semantics of the Java object model as possible, and only includes differences where they make sense for distributed objects. The distributed object system is simple, in that a) distributed objects are easy to use and to implement, and b) the system itself is easily extensible and maintainable. We have designed such a model and implemented a system that supports remote method invocation (RMI) for distributed objects in Java. This system combines aspects of both the Modula-3 Network Objects system lBirrell et aL. 19941and Spring's subcontract [Hamilton et al. 19931 and includes some novel features. To achieve its goal of seamless integration in the language, the system exploits the use of object seialization (pickling) [Riggs et al. 1996] to transmit arguments and return values, and also exploits unique features of Java in order to dynamically load stub code to clients2. The system includes distributed referencecounting garbage collection for distributed objects and will include activation [Object Management Group 1991; Wollrath et al. 19951 of object servers in the future. l. Java and other Java-based names and logos are trademarks of Sun Microsystems, Inc., and refer to Sun's family of Java-branded products and
465 citations
Patent•
29 Nov 1993TL;DR: In this article, the server process identifies an interface to pass to the client process and creates a stub object for receiving a request to invoke a function member of the interface and for invoking the requested function member upon receiving the request.
Abstract: A computer method and system for passing a pointer to an interface from a server process to a client process. In a preferred embodiment, the server process instantiates an object that has multiple interfaces. The server process identifies an interface to pass to the client process and creates a stub object for receiving a request to invoke a function member of the interface and for invoking the requested function member upon receiving the request. The server process then sends an identifier of the stub to the client process. When the client process receives the identifier of the stub, it instantiates a proxy object for receiving requests to invoke a function member of the interface and for sending the request to the identified stub. The client process can then invoke the function members of the interface by invoking function members of the proxy object. The proxy object sends a request to the identified stub. The identified stub then invokes the corresponding function member of the interface.
249 citations
Patent•
21 Nov 2001
TL;DR: In this paper, a method and system for integrating back-end enterprise applications with Web clients is described. But it is not discussed how to integrate CORBA IDL files describing interfaces to objects in the back end enterprise applications.
Abstract: A method and system for integrating back-end enterprise applications with Web clients is disclosed. One preferred embodiment comprises a method for invoking an object, comprising the steps of generating a description of the interface of the object; generating metadata representing the interface of the object from the description; storing the metadata; generating a representation of an invocation of the object in a markup language from the metadata; transmitting the representation of the invocation to a client program configured to invoke the object by interpreting the representation; receiving an invocation from the client program; based on the metadata, interpreting the received invocation. In one preferred embodiment, Web clients comprise Web applications generated automatically from CORBA IDL files describing interfaces to objects in the back-end enterprise applications.
191 citations
Patent•
24 Mar 2005
TL;DR: In this paper, an integration server includes a predefined, fixed system API that pre-defines the low level interfaces between software applications, and the process for integrating these application programs comprises initializing an integration administrator, defining operations and operation resources for transactions between a client and target application programs.
Abstract: An integration server includes a predefined, fixed system API that pre-defines the low level interfaces between software applications. The process for integrating these application programs comprises initializing an integration administrator; defining operations and operation resources for transactions between a client and target application programs; configuring an integration server to accept transactions from the client application program via client code and from the target application via a solution server code; configuring the client code consistent with a client application interface and a predetermined integration server API, and solution server code consistent with a target application interface and the integration server API; and deploying the client code and solution server code. In operation, client code creates an operation object including at least one dataset at a first program using a predetermined integration API; submits the operation object to an integration server; processes the operation object to create a further request object including said dataset, and forwards the request object to a solution program; and processes the request object by the solution program to extract the dataset, forward the dataset for processing at a second program according to functionality associated the operation object, and return a response.
172 citations
Patent•
IBM1
TL;DR: In this paper, the authors present a method and system for storing and managing objects in a digital library system which includes a plurality of clients, an object server for storing an object, a cache server storing an copy of the object, and a centralized server for identifying the object as being stored in the object server and associating one or more of the clients with the cache server.
Abstract: The present invention is directed to a method and system for storing and managing objects, such as binary large objects (blobs) in a digital library system which includes a plurality of clients, an object server for storing an object, a cache server for storing an copy of the object, and a centralized server for storing information identifying the object as being stored in the object server and associating one or more of the clients with the cache server, in which one of the clients, as a requesting client, requests retrieval of an object, a copy of the requested object is sent from the cache server to the requesting client if the object is stored in said cache server, and a copy of said object is sent from the object server to said requesting client if the object is not stored in the cache server; and a copy of the requested object is sent from the object server to the cache server after the object server sends the object to the client, in which the object sent to the client is made available to the client regardless of whether sending of the copy of the object to the cache server is completed.
139 citations
Related Topics (5)
Performance Metrics
| Year | Papers |
|---|---|
| 2017 | 1 |
| 2015 | 2 |
| 2014 | 10 |
| 2013 | 9 |
| 2012 | 6 |
| 2011 | 8 |