Browse Prior Art Database

Adding meta caching property to Java beans

IP.com Disclosure Number: IPCOM000016052D
Original Publication Date: 2002-Sep-08
Included in the Prior Art Database: 2003-Jun-21
Document File: 1 page(s) / 39K

Publishing Venue

IBM

Abstract

Disclosed is a mechanism for efficiently resolving object references over the network. In a client server environment where classes reside on a remote server workstation and are to be invoked on a client workstation, there is no means by which the local application can efficiently determine whether an instantiated Java object has become "dirty". Such is the case for Remote Method Invocation (RMI), tunneling an Java object through a private socket or a multicast socket, utilizing a Java 2 Enterprise Edition (J2EE), or Enterprise Java Bean (EJB) model where the remote server is an application server and the local client is an client container. The effect is that the local application must always use the locally cached Java class or always retrieve the remote Java class whether there were is really a need or not. This mechanism describes a means by which a meta-format can be sent as a property of the remote Java class. This property can be represented using the Extensible Markup Language (XML) and may consist of many different pieces of information, such as the following four basic properties: No cache. This indicates that the consumer of the Java object would always go back to the remote server for a fresh copy. Cache. This indicates that the consumer of the Java object would always use the

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 67% of the total text.

Page 1 of 1

Adding meta caching property to Java beans

   Disclosed is a mechanism for efficiently resolving object references over the network. In a client server environment where classes reside on a remote server workstation and are to be invoked on a client workstation, there is no means by which the local application can efficiently determine whether an instantiated Java object has become "dirty". Such is the case for Remote Method Invocation (RMI), tunneling an Java object through a private socket or a multicast socket, utilizing a Java 2 Enterprise Edition (J2EE), or Enterprise Java Bean (EJB) model where the remote server is an application server and the local client is an client container. The effect is that the local application must always use the locally cached Java class or always retrieve the remote Java class whether there were is really a need or not.

This mechanism describes a means by which a meta-format can be sent as a property of the remote Java class. This property can be represented using the Extensible Markup Language (XML) and may consist of many different pieces of information, such as the following four basic properties:

No cache. This indicates that the consumer of the Java object would always go back

to the remote server for a fresh copy. Cache. This indicates that the consumer of the Java object would always use the

local object, and never go back and see if there is an updated version. Resolve. This indicates that the consumer of the Java object w...