System, method, apparatus and article of manufacture for identity based caching

COPYRIGHT NOTIFICATION

Portions of this patent application contain materials that are subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document, or the patent disclosure, as it appears in the Patent and Trademark Office.

Field of the Invention

This invention relates to a system, method and apparatus for improving response time of a network based transaction session. More particularly, the invention relates to a system, method and apparatus to alleviate network load by use of a location-independent-indexedcache to eliminate repetitive and/or redundant transfers of data objects already resident in the cache.

Background of the Invention

In a number of interactive network applications, it is common for a user to request access to data that is housed on a remote site, but which data has previously been transferred to the user during an earlier session, or an earlier point of time in the present session. The process of requesting the transfer of such information over the network consumes significant time and network resources, particularly if the resource requested is of a substantial size. Therefore, it is desirable to provide a means to recognize that a particular resource stored at a remote location is already available on the users local computer system, and to obtain the desired copy from that local version, rather than performing a network call to obtain a new identical copy. In the past, programs such as World Wide Web browsers (such as Sun Microsystems, Inc.'s HotJava, Netscape Communications Corp.'s Netscape Navigator and Microsoft Corp.'s Internet Explorer) frequently have operated using a cache indexed by a Uniform Resource Locator (URL). By means of this cache, the WWW browser can recognize when a particular URL has been previously referenced, and may present data that had been previously obtained in response to the previous request for the same URL.

However, one shortcoming of this approach is that a URL-indexed cache is capable of providing the user with the previously recovered copy of the requested resource only when the second request for the resource is requesting that resource from the exact location as that from which the resource was initially obtained. That is, if the user requests that a resource be obtained from a new location, a WWW browser equipped with a URL-indexed cache will obtain the requested resource from the specified location, even if the same data is already resident on the user's computer system from a previous transfer from a different location. This approach results in an undesirable amount of redundant data transfers.

This problem is particularly aggravated when the resource requested is not requested under the user's direct control. An example of such a case is where a user requests a particular resource, and that resource in turn requires additional resources. The user has no opportunity to indicate to the system that previously obtained resources should be used instead of redundant copies of the secondary resources. For example, a user may request a particular web page to be displayed, and that page may in turn request transmission of a graphic image to be displayed, or a program (often referred to as an "applet") to be executed in conjunction with the displayed page. The user has no opportunity to indicate to the browser that a previously obtained image file or applet file should be used in lieu of the file located at the remote location.

It is desirable, therefore, to support a remotely located resource that resides on a plurality of computer systems that are identified by a location-independent identifier, thereby allowing reuse of a previously obtained copy of that resource, even if the previously obtained copy was obtained from a different location.

SUMMARY OF THE INVENTION

A system, method, and apparatus for obtaining a copy of a data object is disclosed. A location-independentidentifier associated with the desired data object is obtained, for example, from a primary file that requires a copy of the data object. A cache is interrogated to determine whether a copy of the data object is cached. If the data object is cached, a copy of the cached data object is obtained from the cache. If the data object is not cached, a network call is performed obtain a new copy of the data object.

Additional features of the invention will become apparent upon examination of the description that follows, particularly with reference to the accompanying drawings.

DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, aspects and advantages are better understood from the following detailed description of a preferred embodiment of the invention with reference to the drawings, in which: <ul id="ul0001" list-style="none"><li>Figure <b>1</b> is a block diagram of a representative hardware environment in accordance with a preferred embodiment;</li><li>Figure <b>2</b> depicts a client computer operating a network client program in communication with a server computer;</li><li>Figure <b>3</b> depicts an example of a downloaded HTML document;</li><li>Figure <b>4</b> depicts an operation of obtaining an applet specified by an applet tag;</li><li>Figure <b>5</b> depicts the server response to an HTTP GET request;</li><li>Figure <b>5A</b> depicts the format of a Java applet class file;</li><li>Figure <b>5B</b> depicts the format of a GIF Application Extension data area;</li><li>Figure <b>6</b> depicts transmission of a second HTML document from a second HTTP server to the client computer over a communications link;</li><li>Figure <b>7</b> depicts an example of a second HTML document specifying retrieval of an applet;</li><li>Figure <b>8</b> depicts the process by which the client computer obtains a copy of the desired object from a cache;</li><li>Figure <b>9</b> is a flow chart depicting the overall operation of the invention; and</li><li>Figure <b>10</b> depicts an embodiment of the present invention in which a single cache is shared by a plurality of clients.</li></ul>

DETAILED DESCRIPTION

A preferred embodiment of a system in accordance with the present invention is preferably practiced in the context of a personal computer such as the IBM PS/2, Apple Macintosh computer or UNIX based workstation. A representative hardware environment is depicted in Figure <b>1</b>, which illustrates a typical hardware configuration of a workstation in accordance with a preferred embodiment having a central processing unit <b>10</b>, such as a microprocessor, and a number of other units interconnected via a system bus <b>12</b>. The workstation shown in Figure <b>1</b> includes a Random Access Memory (RAM) <b>14,</b> Read Only Memory (ROM) <b>16</b>, an I/O adapter <b>18</b> for connecting peripheral devices such as disk storage units <b>20</b> to the bus <b>12</b>, a user interface adapter <b>22</b> for connecting a keyboard <b>24</b>, a mouse <b>26</b>, a speaker <b>28</b>, a microphone <b>32</b>, and/or other user interface devices such as a touch screen (not shown) to the bus <b>12</b>, communication adapter <b>34</b> for connecting the workstation to a communication network (e.g., a data processing network) and a display adapter <b>36</b> for connecting the bus <b>12</b> to a display device <b>38</b>. The workstation typically has resident thereon an operating system such as the Microsoft Windows Operating System (OS), the IBM OS/2 operating system, the MAC OS, or UNIX operating system. Those skilled in the art will appreciate that the present invention may also be implemented on platforms and operating systems other than those mentioned.

A preferred embodiment is written using Java, C, and the C++ language and utilizes object oriented programming methodology. Object oriented programming (OOP) has become increasingly used to develop complex applications As OOP moves toward the mainstream of software design and development, various software solutions will need to be adapted to make use of the benefits of OOP. A need exists for these principles of OOP to be applied to a messaging interface of an electronic messaging system such that a set of OOP classes and objects for the messaging interface can be provided.

OOP is a process of developing computer software using objects, including the steps of analyzing the problem, designing the system, and constructing the program. An object is a software package that contains both data and a collection of related structures and procedures. Since it contains both data and a collection of structures and procedures, it can be visualized as a self-sufficient component that does not require other additional structures, procedures or data to perform its specific task. OOP, therefore, views a computer program as a collection of largely autonomous components, called objects, each of which is responsible for a specific task. This concept of packaging data, structures, and procedures together in one component or module is called encapsulation.

In general, OOP components are reusable software modules which present an interface that conforms to an object model and which are accessed at run-time through a component integration architecture. A component integration architecture is a set of architecture mechanisms which allow software modules in different process spaces to utilize each others capabilities or functions. This is generally done by assuming a common component object model on which to build the architecture.

It is worthwhile to differentiate between an object and a class of objects at this point. An object is a single instance of the class of objects, which is often just called a class. A class of objects can be viewed as a blueprint, from which many objects can be formed.

OOP allows the programmer to create an object that is a part of another object. For example, the object representing a piston engine is said to have a composition-relationship with the object representing a piston. In reality, a piston engine comprises a piston, valves and many other components; the fact that a piston is an element of a piston engine can be logically and semantically represented in OOP by two objects.

OOP also allows creation of an object that <img file="EP0834818A2_D0001.tif" />depends from<img file="EP0834818A2_D0002.tif" /> another object. If there are two objects, one representing a piston engine and the other representing a piston engine wherein the piston is made of ceramic, then the relationship between the two objects is not that of composition. A ceramic piston engine does not make up a piston engine. Rather it is merely one kind of piston engine that has one more limitation than the piston engine; its piston is made of ceramic. In this case, the object representing the ceramic piston engine is called a derived object, and it inherits all of the aspects of the object representing the piston engine and adds further limitation or detail to it. The object representing the ceramic piston engine <img file="EP0834818A2_D0003.tif" />depends from<img file="EP0834818A2_D0004.tif" /> the object representing the piston engine. The relationship between these objects is called inheritance.

When the object or class representing the ceramic piston engine inherits all of the aspects of the objects representing the piston engine, it inherits the thermal characteristics of a standard piston defined in the piston engine class. However, the ceramic piston engine object overrides these ceramic specific thermal characteristics, which are typically different from those associated with a metal piston. It skips over the original and uses new functions related to ceramic pistons. Different kinds of piston engines will have different characteristics, but may have the same underlying functions associated with it (e.g., how many pistons in the engine, ignition sequences, lubrication, etc.). To access each of these functions in any piston engine object, a programmer would call the same functions with the same names, but each type of piston engine may have different/overridingimplementations of functions behind the same name. This ability to hide different implementations of a function behind the same name is called polymorphism and it greatly simplifies communication among objects.

With the concepts of composition-relationship, encapsulation, inheritance and polymorphism, an object can represent just about anything in the real world. In fact, our logical perception of the reality is the only limit on determining the kinds of things that can become objects in object-oriented software. Some typical categories are as follows: <ul id="ul0002" list-style="dash" compact="compact"><li>Objects can represent physical objects, such as automobiles in a traffic-flow simulation, electrical components in a circuit-design program, countries in an economics model, or aircraft in an air-traffic-control system.</li><li>Objects can represent elements of the computer-user environment such as windows, menus or graphics objects.</li><li>An object can represent an inventory, such as a personnel file or a table of the latitudes and longitudes of cities.</li><li>An object can represent user-defined data types such as time, angles, and complex numbers, or points on the plane.</li></ul>

With this enormous capability of an object to represent just about any logically separable matters, OOP allows the software developer to design and implement a computer program that is a model of some aspects of reality, whether that reality is a physical entity, a process, a system, or a composition of matter. Since the object can represent anything, the software developer can create an object which can be used as a component in a larger software project in the future.

If 90% of a new OOP software program consists of proven, existing components made from preexisting reusable objects, then only the remaining 10% of the new software project has to be written and tested from scratch. Since 90% already came from an inventory of extensively tested reusable objects, the potential domain from which an error could originate is 10% of the program. As a result, OOP enables software developers to build objects out of other, previously built, objects.

This process closely resembles complex machinery being built out of assemblies and sub-assemblies. OOP technology, therefore, makes software engineering more like hardware engineering in that software is built from existing components, which are available to the developer as objects. All this adds up to an improved quality of the software as well as an increased speed of its development.

Programming languages are beginning to fully support the OOP principles, such as encapsulation, inheritance, polymorphism, and composition-relationship. With the advent of the C++ language, many commercial software developers have embraced OOP. C++ is an OOP language that offers a fast, machine-executable code. Furthermore, C++ is suitable for both commercial-application and systems-programming projects. For now, C++ appears to be the most popular choice among many OOP programmers, but there is a host of other OOP languages, such as Smalltalk, common lisp object system (CLOS), and Eiffel. Additionally, OOP capabilities are being added to more traditional popular computer programming languages such as Pascal

The benefits of object classes can be summarized, as follows: <ul id="ul0003" list-style="dash" compact="compact"><li><i>Objects</i> and their corresponding classes break down complex programming problems into many smaller, simpler problems.</li><li><i>Encapsulation</i> enforces data abstraction through the organization of data into small, independent objects that can communicate with each other. Encapsulation protects the data in an object from accidental damage, but allows other objects to interact with that data by calling the object's member functions and structures.</li><li><i>Subclassing</i> and inheritance make it possible to extend and modify objects through deriving new kinds of objects from the standard classes available in the system. Thus, new capabilities are created without having to start from scratch.</li><li><i>Polymorphism</i> and multiple inheritance make it possible for different programmers to mix and match characteristics of many different classes and create specialized objects that can still work with related objects in predictable ways.</li><li><i>Class hierarchies</i> and containment hierarchies provide a flexible mechanism for modeling real-world objects and the relationships among them.</li><li><i>Libraries</i> of reusable classes are useful in many situations, but they also have some limitations. For example:</li><li><i>Complexity.</i> In a complex system, the class hierarchies for related classes can become extremely confusing, with many dozens or even hundreds of classes.</li><li><i>Flow of control.</i> A program written with the aid of class libraries is still responsible for the flow of control (i.e., it must control the interactions among all the objects created from a particular library). The programmer has to decide which functions to call at what times for which kinds of objects.</li><li><i>Duplication of effort.</i> Although class libraries allow programmers to use and reuse many small pieces of code, each programmer puts those pieces together in a different way. Two different programmers can use the same set of class libraries to write two programs that do exactly the same thing but whose internal structure (i.e., design) may be quite different, depending on hundreds of small decisions each programmer makes along the way. Inevitably, similar pieces of code end up doing similar things in slightly different ways and do not work as well together as they should.</li></ul>

Class libraries are very flexible. As programs grow more complex, more programmers are forced to reinvent basic solutions to basic problems over and over again. A relatively new extension of the class library concept is to have a framework of class libraries. This framework is more complex and consists of significant collections of collaborating classes that capture both the small scale patterns and major mechanisms that implement the common requirements and design in a specific application domain. They were first developed to free application programmers from the chores involved in displaying menus, windows, dialog boxes, and other standard user interface elements for personal computers.

Frameworks also represent a change in the way programmers think about the interaction between the code they write and code written by others In the early days of procedural programming, the programmer called libraries provided by the operating system to perform certain tasks, but basically the program executed down the page from start to finish, and the programmer was solely responsible for the flow of control. This was appropriate for printing out paychecks, calculating a mathematical table, or solving other problems with a program that executed in just one way.

The development of graphical user interfaces began to turn this procedural programming arrangement inside out. These interfaces allow the user, rather than program logic, to drive the program and decide when certain actions should be performed. Today, most personal computer software accomplishes this by means of an event loop which monitors the mouse, keyboard, and other sources of external events and calls the appropriate parts of the programmer's code according to actions that the user performs. The programmer no longer determines the order in which events occur. Instead, a program is divided into separate pieces that are called at unpredictable times and in an unpredictable order. By relinquishing control in this way to users, the developer creates a program that is much easier to use. Nevertheless, individual pieces of the program written by the developer still call libraries provided by the operating system to accomplish certain tasks, and the programmer must still determine the flow of control within each piece after it's called by the event loop. Application code still <img file="EP0834818A2_D0005.tif" />sits on top of<img file="EP0834818A2_D0006.tif" /> the system.

Even event loop programs require programmers to write a lot of code that should not need to be written separately for every application. The concept of an application framework carries the event loop concept further. Instead of dealing with all the nuts and bolts of constructing basic menus, windows, and dialog boxes and then making these things all work together, programmers using application frameworks start with working application code and basic user interface elements in place Subsequently, they build from there by replacing some of the generic capabilities of the framework with the specific capabilities of the intended application.

Application frameworks reduce the total amount of code that a programmer has to write from scratch. However, because the framework is really a generic application that displays windows, supports copy and paste, and so on, the programmer can also relinquish control to a greater degree than event loop programs permit. The framework code takes care of almost all event handling and flow of control, and the programmer's code is called only when the framework needs it (e.g., to create or manipulate a proprietary data structure).

A programmer writing a framework program not only relinquishes control to the user (as is also true for event loop programs), but also relinquishes the detailed flow of control within the program to the framework. This approach allows the creation of more complex systems that work together in interesting ways, as opposed to isolated programs, having custom code, being created over and over again for similar problems.

Thus, as is explained above, a framework basically is a collection of cooperating classes that make up a reusable design solution for a given problem domain It typically includes objects that provide default behavior (e.g., for menus and windows), and programmers use it by inheriting some of that default behavior and overriding other behavior so that the framework calls application code at the appropriate times. There are three main differences between frameworks and class libraries: <ul id="ul0004" list-style="dash" compact="compact"><li><i>Behavior versus protocol.</i> Class libraries are essentially collections of behaviors that you can call when you want those individual behaviors in your program. A framework, on the other hand, provides not only behavior but also the protocol or set of rules that govern the ways in which behaviors can be combined, including rules for what a programmer is supposed to provide versus what the framework provides.</li><li><i>Call versus override.</i> With a class library, the code the programmer writes instantiates objects and calls their member functions It's possible to instantiate and call objects in the same way with a framework (i.e., to treat the framework as a class library), but to take full advantage of a framework's reusable design, a programmer typically writes code that overrides and is called by the framework. The framework manages the flow of control among its objects. Writing a program involves dividing responsibilities among the various pieces of software that are called by the framework rather than specifying how the different pieces should work together.</li><li><i>Implementation versus design.</i> With class libraries, programmers reuse only implementations, whereas with frameworks, they reuse design. A framework embodies the way a family of related programs or pieces of software work. It represents a generic design solution that can be adapted to a variety of specific problems in a given domain. For example, a single framework can embody the way a user interface works, even though two different user interfaces created with the same framework might solve quite different interface problems.</li></ul>

Thus, through the development of frameworks for solutions to various problems and programming tasks, significant reductions in the design and development effort for software can be achieved. A preferred embodiment of the invention utilizes Hypertext Markup Language (HTML) to implement documents on the Internet together with a general-purpose secure communication protocol for a transport medium between the client and the merchant. HTML is a simple data format used to create hypertext documents that are portable from one platform to another. HTML documents are SGML documents with generic semantics that are appropriate for representing information from a wide range of domains. HTML has been in use by the World-Wide Web global information initiative since 1990. HTML is an application of ISO Standard 8879:1986 Information Processing Text and Office Systems; Standard Generalized Markup Language (SGML).

To date, Web development tools have been limited in their ability to create dynamic Web applications which span from client to server and interoperate with existing computing resources. Until recently, HTML has been the dominant technology used in development of Web-based solutions. However, HTML has proven to be inadequate in the following areas: <ul id="ul0005" list-style="none" compact="compact"><li>o Poor performance;</li><li>o Restricted user interface capabilities;</li><li>o Can only produce static Web pages;</li><li>o Lack of interoperability with existing applications and data; and</li><li>o Inability to scale.</li></ul>

Sun Microsystem's Java language solves many of the client-side problems by: <ul id="ul0006" list-style="none" compact="compact"><li>o Improving performance on the client side;</li><li>o Enabling the creation of dynamic, real-time Web applications; and</li><li>o Providing tile ability to create a wide variety of user interface components.</li></ul>

With Java, developers can create robust User Interface (UI) components. Custom "widgets" (e.g. real-time stock tickers, animated icons, etc.) can be created, and client-side performance is improved. Unlike HTML, Java supports the notion of client-side validation, offloading appropriate processing onto the client for improved performance. Dynamic, real-time Web pages can be created. Using the above-mentioned custom UI components, dynamic Web pages can also be created.

Sun's Java language has emerged as an industry-recognized language for "programming the Internet." Sun defines Java as: <img file="EP0834818A2_D0007.tif" />a simple, object-oriented, distributed, interpreted, robust, secure, architecture-neutral, portable, high-performance, multithreaded, dynamic, buzzword-compliant, general-purpose programming language. Java supports programming for the Internet in the form of platform-independent Java applets.<img file="EP0834818A2_D0008.tif" /> Java applets are small, specialized applications that comply with Sun's Java Application Programming Interface (API) allowing developers to add "interactive content" to Web documents (e.g. simple animations, page adornments, basic games, etc.). Applets execute within a Java-compatible browser (e.g. Netscape Navigator) by copying code from the server to client. From a language standpoint, Java's core feature set is based on C++. Sun's Java literature states that Java is basically "C++, with extensions from Objective C for more dynamic method resolution".

Another technology that provides similar function to Java is provided by Microsoft and ActiveX Technologies, to give developers and Web designers wherewithal to build dynamic content for the Internet and personal computers. ActiveX includes tools for developing animation, 3-D virtual reality, video and other multimedia content. The tools use Internet standards, work on multiple platforms, and are being supported by over 100 companies, The group's building blocks are called ActiveX Controls, small, fast components that enable developers to embed parts of software in hypertext markup language (HTML) pages. ActiveX Controls work with a variety of programming languages including Microsoft Visual C++, Borland Delphi, Microsoft Visual Basic programming system and, in the future, Microsoft's development tool for Java, code named "Jakarta." ActiveX Technologies also includes ActiveX Server Framework, allowing developers to create server applications. One of ordinary skill in the art will readily recognize that ActiveX could be substituted for Java without undue experimentation to practice the invention.

Figure <b>2</b> depicts a client computer <b>210</b> operating a network client program, such as a web browser, in communication with server computer <b>215.</b> Server <b>215</b> may be, for example, a hypertext transport protocol ("HTTP") server. Server <b>215</b> is named "SYSA" This denotes that the server is addressed with a name such as SYSA, or is located externally to the client's network, for example, in a system with the name SYSA.COM. Server <b>215</b> is in communication with client <b>210</b> using a communications link <b>220</b> operating, for example, using the HTTP protocol and the Transmission Control Protocol and Internet Protocol ("TCP" and "IP," respectively, or collectively "TCP/IP"). HTTP is described in R. Fielding, et al., <i>Hypertext Transfer Protocol: HTTP/ 1.1</i> (June 3, 1996) (draft), the disclosure of which is hereby incorporated by reference. TCP is described in Information Sciences Institute, <i>RFC 793: Transmission Control Protocol DARPA Internet Program Protocol Specification</i> (September 1981), the disclosure of which is hereby incorporated by reference. IP is described in Information Sciences Institute, <i>RFC 791: Internet Protocol DARPA Internet Program Protocol Specification</i> (September 1981), the disclosure of which is hereby incorporated by reference.

As depicted in Figure <b>2</b>, server <b>215</b> is transferring a copy of document <b>225</b>, named PAGE1.HTML, to client <b>210,</b> in response to a previous HTTP GET request (not shown) by client <b>210.</b> Client <b>210</b> is equipped with a cache file <b>230</b> indexed by a cache table <b>235</b>. Cache table <b>235</b> is a table used to index cache <b>230</b>. Cache table <b>235</b> comprises a plurality of rows <b>238</b> and columns <b>240</b>. Each row <b>238</b> is used to describe a cached element, such as downloaded HTML document <b>225</b>. Columns <b>240</b> include a URI column <b>245</b>, an OID column <b>247</b>, and a cache pointer column <b>249</b>. The use of the cache table will be described in further detail below, however, in summary, URI column <b>245</b> contains a representation of a location code of a cached resource. Typically this will be a representation of a Uniform Resource Identifier ("URI"), such as a Uniform Resource Locator ("URL"), or any other indicator of the location of the cached resource. The syntax and semantics of URLs are described in Berners-Lee, et al., <i>RFC 1738: Uniform Resource Locators (URL)</i> (December 1994), the disclosure of which is hereby incorporated by reference.

OID column <b>247</b> contains an object identifier, if any for the cached resource, or is null if no object identifier is associated with the cached resource. Cache pointer column <b>249</b> contains a pointer to the cache element in the cache. This may be, for example, the name of a file located within a specific predetermined cache directory or cache device, or it may be a specification of a location within a larger file of a particular portion of the file corresponding to the cached resource In addition, the cache table will typically contain additional fields used to manage and optimize a cache table, such as indicators of whether a particular cache row <b>238</b> is in use, its frequency of reference, etc. Such fields are not a portion of the present invention and are not herein described.

As depicted in Figure <b>2</b>, client <b>210</b> transfers a copy of downloaded file <b>225</b> to cache <b>230</b> as shown by arrow <b>260</b>. As depicted in Figure <b>2</b>, a copy of document <b>225</b> is cached at location <b>265</b>, and cache table row <b>238-1</b> is updated to reflect the cache. In particular, for cache table row <b>238-1</b>, URI column <b>245</b> is set to the value of the URI for the retrieved document. Column <b>247</b> is set to null because, as will be described in further detail, no OID has been associated with this resource. Column <b>249</b> has been set to point to cached element <b>265</b>.

Figure <b>3</b> depicts an example of downloaded document <b>225</b>. In the depicted example, the file is in Hypertext Markup Language ("HTML"). The HTML format is described in Berners-Lee, et al., <i>RFC 1866: Hypertext Markup Language - 2.0</i> (November 1995), which is hereby incorporated by reference. The HTML document <b>225</b> comprises a plurality of HTML tags <b>310</b> and text <b>320</b> to be rendered and displayed. With the exception of the applet tag <b>330</b>, all of HTML tags <b>310</b> are known and described in Berners-Lee, and are not further described herein. Applet tag <b>330</b> is an HTML tag that is used to specify an applet that should be loaded and executed when HTML document <b>225</b> is rendered and displayed Specifically applet tag <b>330</b> is an extension to HTML devised by Sun Microsystems, Inc. of Mountain View, California. Typically, applets are written in a platform-independentobject-oriented language such as Sun Microsystem's Java language. A Java applet is generally transported in the Sun's CLASS-format file. Applet tag <b>330</b> contains four parameters: CODE parameter <b>340</b>, WIDTH parameter <b>342</b>, HEIGHT parameter <b>344</b>, and OID parameter <b>350</b>. The CODE, WIDTH, and HEIGHT parameters are known in the art. The CODE parameter <b>340</b> is used to specify the name of a program file to be downloaded from the same server location as HTML document <b>225</b>. In the example depicted, CODE parameter <b>340</b> indicates that the program named FOO.CLASS is to be obtained from the SYSA server <b>215</b> because the web page was part of the HTML information. WIDTH parameter <b>342</b> and HEIGHT parameter <b>344</b> indicate the size of screen area where the output of the applet will be displayed. In the example shown, an area 300 pixels wide and 100 pixels high is specified.

The OID parameter <b>350</b> is not previously known. OID parameter <b>350</b> is used to specify an object identifier. The object identifier is a unique identifier associated with a particular object, The OID associated with a particular object is guaranteed to be unique. A preferred method of specifying the OID is using Abstract Syntax Notation One ("ASN. 1"), as described in ISO 8824, and the ASN. 1 Basic Encoding Rules ("BER") as described in ISO 8825. ASN. 1 and BER provide for an "object identifier" datatype.

The ASN. 1 object identifier is in the form of a series of integers separated by decimal points. Each integer represents a node on an ASN. 1 object identifier tree. The ASN. 1 object identifier tree is a structure with a root node, arcs beneath that node to other nodes, with arcs beneath them and so on. As specified in the ASN. 1 standard, each node is assigned to some responsible body that allocates arcs and nodes beneath it. The body ensures that all the arcs beneath its node are numbered sequentially starting from 0 or 1 and that each node beneath it is either assigned to some responsible body or is assigned to name a particular object. In the example shown, the OID has a value of 1.1.999999.72.6.3. The first integer, 1, has been allocated to the International Standards Organization ("ISO"). The ISO, therefore, has the responsibility for allocating every OID beginning with the integer 1. The second integer 1 indicates that this object is within an ASN. 1 hierarchy allocated to a "registration authority" ("RA"). A registration authority is an organization that is responsible for the allocation of any further ASN. 1 OIDs within its name space. In the example shown, the fictitious registration authority code 999999 is used to depict that a particular responsibility authority having been assigned a code 999999 is responsible for any object identifiers below this level The remaining integers (72, 6, and 3) are arbitrary integers organized according to a functional scheme selected by the registration authority corresponding to RA code 999999, and guaranteed by the registration authority to be unique in the world. ASN.1, BER, the ASN.1 object identifier, and the ASN.1 object identifier tree are known constructs and are described in their respective standards and, for example, in Larmouth, <i>Understanding OSI</i>(International Thomson Computer Press, 1996), pp. 151-160, hereby incorporated by reference.

It will be seen from Figure <b>3</b>, therefore, that the desired applet may be referred to either by a particular known location (file name FOO.CLASS on server SYSA) or by its ASN.1 object identifier (1.1.999999.72.6.3).

Figure <b>4</b> depicts an operation of obtaining the applet specified by applet tag <b>330</b> of Figure <b>3</b>. In the example depicted, the applet specified by applet tag <b>330</b> has not been previously obtained, and therefore is unavailable from cache <b>230</b> of Figure <b>2.</b> Therefore, as depicted in Figure <b>4</b>, client <b>210</b> issues an HTTP GET request for the resource named FOO.CLASS on connection <b>220</b> to server SYSA <b>215</b>.

Figure <b>5</b> depicts the server response to the GET request. Server <b>215</b> transmits a copy <b>510</b> of the FOO.CLASS object on communications line <b>220</b> to client computer <b>210</b>. Client computer <b>210</b> places a copy of received file <b>510</b> in cache <b>230</b> as cache element <b>520</b>. Client computer <b>210</b> then updates cache table <b>235</b> to reflect the cache update. Specifically, client computer <b>210</b> updates row <b>238-2</b> to reflect newly added element <b>520</b>.

Client computer <b>210</b> updates cache table row <b>238-2</b> as follows. URI column <b>245</b> is set to the value of the URI from which the file was retrieved. OID column <b>247</b> is updated with the object identifier value for the object received. Finally, column <b>249</b> is updated with a pointer to the cache element <b>520</b> within cache <b>230</b>.

Generally, an object that is received from a server may have an OID encoded into it, so that a client computer such as client computer <b>210</b> can discover the object's OID even if no OID had been specified prior to the transfer. The OID may be encoded, for example, in a predetermined position or field within the object, or may be stored on the server separately from the object and included by the server by encoding it into the HTTP GET response

The Java CLASS format is highly structured and is particularly well-suited for the purpose of encoding an OID into an applet file. The Java CLASS format is described in Sun Microsystem's <i>Java Virtual Machine Specification, Release 1.0 Beta DRAFT</i>(August 21, 1995) the disclosure of which is hereby incorporated by reference.

Each class file contains the compiled version of either a Java class or a Java interface. An interpreter or "virtual machine" designed to execute a Java applet supports all class files that conform to this format.

A Java class file comprises a stream of 8-bit bytes. All 16-bit and 32-bit quantities are constructed by reading in two or four 8-bit bytes, respectively. The bytes are joined together in network (big-endian) order, where the high bytes come first. This format is supported by the Java java.io.DataInput and java.io.DataOutputinterfaces, and classes such as java.io.DataInputStream andjava.io.DataOutputstream.

The class file format is described here using a structure notation. Successive fields in the structure appear in the external representation without padding or alignment. Variable size arrays, often of variable sized elements are called tables and are commonplace in these structures The types u1, u2, and u4 mean an unsigned one-, two-, or four-byte quantity, respectively, which are read by method such as readUnsignedByte, readUnsignedShort and readInt of the java.io.DataInputinterface.

Figure 5A depicts the format of a class file <b>560</b>, which is structured as follows:<img file="EP0834818A2_D0009.tif" /><img file="EP0834818A2_D0010.tif" />

magic

The "magic" field <b>561</b> is four bytes in length and is used to identify the file as a Java class-format file. The magic field has the value 0xCAFEBABE.

minor_version and major version

The minor_version field <b>562</b> and major_version field <b>563</b> contain the version number of the Java compiler that produced this class file. The combination of the two fields may be interrogated by a virtual machine to determine whether it is capable of executing the applet. An implementation of the virtual machine will normally support some range of minor version numbers 0-n of a particular major version number. If the minor version number is incremented, the new code won't run on the old virtual machines, but it is possible to make a new virtual machine which can run versions up to version number n+1. A change of the major version number indicates a major incompatible change, one that requires a different virtual machine that may not support the old major version in any way.

constant_pool_count

The constant_pool_countfield <b>564</b> indicates the number of entries in the constant pool <b>565</b> in the class file.

constant_pool

The constant pool <b>565</b> is a table of values The values in the constant pool <b>565</b> comprise various string constants, classnames, field names, and others that are referred to by the class structure or by the executable code in the applet. The first constant pool entry, denoted as constant_pool[0], is always unused by the compiler, and may be used by an implementation for any purpose.

Each of the constant_pool entries 1 through constant_pool_count-1 is a variable-length entry, whose format is indicated by the first <img file="EP0834818A2_D0011.tif" />tag<img file="EP0834818A2_D0012.tif" /> byte, according to the following table: <tables id="tabl0001" num="0001"><table frame="all"><tgroup cols="3" colsep="1" rowsep="0"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row rowsep="1"><entry namest="col1" nameend="col1" align="center">Value</entry><entry namest="col2" nameend="col2" align="center">Constant Type</entry><entry namest="col3" nameend="col3" align="center">Meaning</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">1</entry><entry namest="col2" nameend="col2" align="left">CONSTANT_Utf8</entry><entry namest="col3" nameend="col3" align="left">utf-8 format string</entry></row><row><entry namest="col1" nameend="col1" align="left">2</entry><entry namest="col2" nameend="col2" align="left">CONSTANT_Unicode</entry><entry namest="col3" nameend="col3" align="left">unicode format string</entry></row><row><entry namest="col1" nameend="col1" align="left">3</entry><entry namest="col2" nameend="col2" align="left">CONSTANT_Integer</entry><entry namest="col3" nameend="col3" align="left">integer</entry></row><row><entry namest="col1" nameend="col1" align="left">4</entry><entry namest="col2" nameend="col2" align="left">CONSTANT_Float</entry><entry namest="col3" nameend="col3" align="left">floating point</entry></row><row><entry namest="col1" nameend="col1" align="left">5</entry><entry namest="col2" nameend="col2" align="left">CONSTANT_Long</entry><entry namest="col3" nameend="col3" align="left">long integer</entry></row><row><entry namest="col1" nameend="col1" align="left">6</entry><entry namest="col2" nameend="col2" align="left">CONSTANT_Double</entry><entry namest="col3" nameend="col3" align="left">double floating point</entry></row><row><entry namest="col1" nameend="col1" align="left">7</entry><entry namest="col2" nameend="col2" align="left">CONSTANT_Class</entry><entry namest="col3" nameend="col3" align="left">class</entry></row><row><entry namest="col1" nameend="col1" align="left">8</entry><entry namest="col2" nameend="col2" align="left">CONSTANT_String</entry><entry namest="col3" nameend="col3" align="left">string</entry></row><row><entry namest="col1" nameend="col1" align="left">9</entry><entry namest="col2" nameend="col2" align="left">CONSTANT_Fieldref</entry><entry namest="col3" nameend="col3" align="left">field reference</entry></row><row><entry namest="col1" nameend="col1" align="left">10</entry><entry namest="col2" nameend="col2" align="left">CONSTANT_Methodref</entry><entry namest="col3" nameend="col3" align="left">method reference</entry></row><row><entry namest="col1" nameend="col1" align="left">11</entry><entry namest="col2" nameend="col2" align="left">CONSTANT_InterfaceMethodref</entry><entry namest="col3" nameend="col3" align="left">interface method reference</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">12</entry><entry namest="col2" nameend="col2" align="left">CONSTANT_NameAndType</entry><entry namest="col3" nameend="col3" align="left">name and type</entry></row></tbody></tgroup></table></tables>

A utf-8 format string constant pool entry represents a constant character string value. Utf-8 strings are encoded so that strings containing only non-null ASCII characters, can be represented using only one byte per character, but characters of up to 16 bits can still be represented.

All characters in the range 0x0001 to 0x007F are represented by a single byte, in which bit 0 is set to binary '0' and in which bits 1-7 represent the ASCII code 0x0001 to 0x007F, respectively. The null character 0x0000 and characters in the range 0x0080 to 0x07FF are represented by a pair of two bytes, or 16 bits, denoted here as bits 0-15. Bits 0-2 are set to binary '110' and bits 8-9 are set to binary '10'. The remaining eleven bits 3-7 and 10-15 correspond respectively to the low-order eleven bits in the character to be encoded.

Characters in the range 0x0800 to 0xFFFF are represented by three bytes, or 24 bits, denoted here as bits 0-23. Bits 0-3, 8-9 and 16-17 are set to binary values '1110', '10', and '10', respectively. The remaining 16 bits 4-7, 10-15 and 18-23 correspond to the 16 bits in the character to be encoded.

The null character 0x00 is encoded in two-byte format rather than one-byte, with the result that encoded strings never have embedded nulls. Only one-byte, two-byte, and three-byte formats are used; longer utf-8 formats are unrecognized.

A utf-8 string is structured as follows:<img file="EP0834818A2_D0013.tif" />

The tag field has the constant value 0x'0001' indicating a utf-8 encoded string. The length field is a two-byte field indicating the length of the string The bytes field is the encoded string.

A UNICODE string constant pool entry represents a constant unencoded character string value. A UNICODE string is structured as follows:<img file="EP0834818A2_D0014.tif" />

The tag field has the constant value 0x'0002' indicating a unicode-format string. The length field is a two-byte field indicating the length of the string. The bytes field is the string value.

An integer constant pool entry represents a four-byte integer. The constant pool entry is structured as follows:<img file="EP0834818A2_D0015.tif" /><img file="EP0834818A2_D0016.tif" />

The tag field has the constant value 0x'0003' indicating a integer. The bytes field is the integer value.

A float constant pool entry represents a four-byte floating-point number. The constant pool entry is structured as follows:<img file="EP0834818A2_D0017.tif" />

The tag field has the constant value 0x'0004' indicating a floating-point number. The bytes field is the floating-point value.

A long integer constant pool entry represents an eight-byte integer. The constant pool entry is structured as follows:<img file="EP0834818A2_D0018.tif" />

The tag field has the constant value 0x'0005' indicating a long integer. The high_bytes and low_bytes fields together make up the integer value. A long integer constant pool entry takes up two spots in the constant pool <b>565</b>. If this is the nth entry in the constant pool <b>565</b>, then the next entry will be numbered n+2.

A double float constant pool entry represents an eight-byte floating-point number. The constant pool entry is structured as follows:<img file="EP0834818A2_D0019.tif" />

The tag field has the constant value 0x'0006' indicating a double floating-point number. The high_bytes and low_bytes fields together make up the floating-point value. A double float constant pool entry takes up two spots in the constant pool <b>565.</b> If this is the nth entry in the constant pool <b>565,</b> then the next entry will be numbered n+2.

A class constant pool entry represents a Java class or an interface The constant pool entry is structured as follows:<img file="EP0834818A2_D0020.tif" /><img file="EP0834818A2_D0021.tif" />

The tag field has the constant value 0x'0007' indicating a class. The name_index field is a subscript into the constant pool <b>565</b>, to a utf-8 format string constant that gives the string name of the class.

A string constant pool entry represents Java objects of the built-in Java type "String." The constant pool entry is structured as follows:<img file="EP0834818A2_D0022.tif" />

The tag field has the constant value 0x'0008' indicating a string. The string_index field is a subscript into the constant pool <b>565</b>, to a utf-8 format string constant that gives the value to which the String-type object is initialized.

A field constant pool entry, method reference constant pool entry, and interface method reference constant pool entry represent references to Java fields, methods, and interface methods, respectively. The constant pool entries are structured as follows:<img file="EP0834818A2_D0023.tif" /><img file="EP0834818A2_D0024.tif" />

The tag field has the constant value 0x'0009', 0x'000A', or 0x'000B', indicating a field reference, method reference, or interface method reference, respectively. The class_index field is a subscript into the constant pool <b>565</b>, to a class constant that is used to identify the name of the class or interface containing the field or method. The name_and_type_indexfield is a subscript into the constant pool <b>565</b>, to a NameAndType constant that is used to identify the name and signature of the field or method.

A NameAndType constant pool entry represents a field or method without indicating the class to which the name or field, as the case may be, belongs. The constant pool entry is structured as follows:<img file="EP0834818A2_D0025.tif" />

The tag field has the constant value 0x'000C' indicating a NameAndType entry. The name_index field is a subscript into the constant pool <b>565</b>, to a utf-8 format string constant that gives the name of the field or method. The signature_index field is a subscript into the constant pool <b>565</b>, to a utf-8 format string constant that gives a signature of the field or method. The signature, in this context, refers to a string that represents a type of a method, field or array. The field signature represents the value of an argument to a function or the value of a variable. A return-type signature represents the return value from a method. An argument signature represents an argument passed to a method. A method signature comprises one or more arguments signatures and a return signature, thereby representing the arguments expected by a method, and the value that it returns.

The structure and self-referential nature of the cell pool thereby provides great flexibility in implementation of data encoded in an applet file.

access_flags

The access_flags field <b>566</b> contains a mask of up to sixteen modifiers used with class, method, and field declarations. The same encoding is used on similar fields in field_info and method_info as described below The access_flags field is encoded as follows: <tables id="tabl0002" num="0002"><table frame="all"><tgroup cols="4" colsep="1" rowsep="0"><colspec colnum="1" colname="col1" colwidth="39.37mm" /><colspec colnum="2" colname="col2" colwidth="39.37mm" /><colspec colnum="3" colname="col3" colwidth="39.37mm" /><colspec colnum="4" colname="col4" colwidth="39.37mm" /><thead valign="top"><row rowsep="1"><entry namest="col1" nameend="col1" align="center">Flag Name</entry><entry namest="col2" nameend="col2" align="right">Value</entry><entry namest="col3" nameend="col3" align="center">Meaning</entry><entry namest="col4" nameend="col4" align="center">Used By</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">ACC_PUBLIC</entry><entry namest="col2" nameend="col2" align="right">0x0001</entry><entry namest="col3" nameend="col3" align="left">Visible to everyone</entry><entry namest="col4" nameend="col4" align="left">Class, Method, Variable</entry></row><row><entry namest="col1" nameend="col1" align="left">ACC_PRIVATE</entry><entry namest="col2" nameend="col2" align="right">0x0002</entry><entry namest="col3" nameend="col3" align="left">Visible only to the defining class</entry><entry namest="col4" nameend="col4" align="left">Method, Variable</entry></row><row><entry namest="col1" nameend="col1" align="left">ACC_PROTECTED</entry><entry namest="col2" nameend="col2" align="right">0x0004</entry><entry namest="col3" nameend="col3" align="left">Visible to subclasses</entry><entry namest="col4" nameend="col4" align="left">Method, Variable</entry></row><row><entry namest="col1" nameend="col1" align="left">ACC_STATIC</entry><entry namest="col2" nameend="col2" align="right">0x0008</entry><entry namest="col3" nameend="col3" align="left">Variable or method is static</entry><entry namest="col4" nameend="col4" align="left">Method, Variable</entry></row><row><entry namest="col1" nameend="col1" align="left">ACC_FINAL</entry><entry namest="col2" nameend="col2" align="right">0x0010</entry><entry namest="col3" nameend="col3" align="left">No further subclassing, overriding, or assignment after initialization</entry><entry namest="col4" nameend="col4" align="left">Class, Method, Variable</entry></row><row><entry namest="col1" nameend="col1" align="left">ACC_SYNCHRONIZED</entry><entry namest="col2" nameend="col2" align="right">0x0020</entry><entry namest="col3" nameend="col3" align="left">Wrap use in monitor lock</entry><entry namest="col4" nameend="col4" align="left">Method</entry></row><row><entry namest="col1" nameend="col1" align="left">ACC_VOLATILE</entry><entry namest="col2" nameend="col2" align="right">0x0040</entry><entry namest="col3" nameend="col3" align="left">Can't cache</entry><entry namest="col4" nameend="col4" align="left">Variable</entry></row><row><entry namest="col1" nameend="col1" align="left">ACC_TRANSIENT</entry><entry namest="col2" nameend="col2" align="right">0x0080</entry><entry namest="col3" nameend="col3" align="left">Not to be written or read by a persistent object manager</entry><entry namest="col4" nameend="col4" align="left">Variable</entry></row><row><entry namest="col1" nameend="col1" align="left">ACC_NATIVE</entry><entry namest="col2" nameend="col2" align="right">0x0100</entry><entry namest="col3" nameend="col3" align="left">Implemented in a language other than Java</entry><entry namest="col4" nameend="col4" align="left">Method</entry></row><row><entry namest="col1" nameend="col1" align="left">ACC_INTERFACE</entry><entry namest="col2" nameend="col2" align="right">0x0200</entry><entry namest="col3" nameend="col3" align="left">Is an interface</entry><entry namest="col4" nameend="col4" align="left">Class</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">ACC_ABSTRACT</entry><entry namest="col2" nameend="col2" align="right">0x0400</entry><entry namest="col3" nameend="col3" align="left">No body provided</entry><entry namest="col4" nameend="col4" align="left">Class, Method</entry></row></tbody></tgroup></table></tables>

this_class

The this_class field <b>567</b> is an index into the constant pool <b>565</b>; constant_pool[this_class]must be of type CONSTANT_class.

super_class

The super_class <b>568</b> field is an index into the constant pool <b>565</b>. If the value of super_class field <b>568</b> is nonzero, then constant_pool[super_class]must be a class, and gives the index of this class's superclass (that is, the class from which the present class is derived) in the constant pool <b>565</b>. If the value of super_class field <b>568</b> is zero, then the class being defined must be java.lang.Object, and it has no superclass.

interfaces_count

The interfaces_count field <b>569</b> gives the number of interfaces that this class implements.

interfaces table

Each value in interfaces table <b>570</b> is an index into the constant pool <b>565</b>. If an table value is nonzero(interfaces[i] != 0, where 0 &lt;= i &lt; interfaces_count), then constant_pool(interfaces(i)]must be an interface that this class implements.

fields_count

The fields_count field <b>571</b> gives the number of instance variables, both static and dynamic, defined by the this class field. The fields table <b>572</b> includes only those variables that are defined explicitly by this class. It does not include those instance variables that are accessible from this class but are inherited from superclasses.

fields table

Each value in the fields table <b>572</b> is a more complete description of a field in the class. Each field is described by a variable length field_info structure. The format of this structure is as follows:<img file="EP0834818A2_D0026.tif" />

The access_flags field is a set of sixteen flags used by classes, methods, and fields to describe various properties and how they many be accessed by methods in other classes. This field has the same names, values and meanings as the access_flags field <b>566</b> previously disclosed.

The possible flags that can be set for a field are ACC_PUBLIC, ACC_PRIVATE, ACC_PROTECTED, ACC_STATIC, ACC_FINAL, ACC_VOLATILE, and ACC_TRANSIENT. At most one of ACC_PUBLIC, ACC_PROTECTED, and ACC_PRIVATE can be set for any method.

The name_index field is a subscript used to index into the constant pool <b>565</b> indicating a CONSTANT_Utf8 string, which is the name of the field.

The signature_indexfield is a subscript that is used to index into the constant pool <b>565</b> to indicate a CONSTANT_Utf8 string, which is the signature of the field.

The attributes_countfield indicates the number of additional attributes about this field.

The attributes field represents the attributes of a particular field represented by the field_info structure. A field can have any number of optional attributes associated with it. For example, the <img file="EP0834818A2_D0027.tif" />ConstantValue<img file="EP0834818A2_D0028.tif" /> attribute, which indicates that this field is a static numeric constant, indicates the constant value of that field.

methods_count

The methods_countfield <b>573</b> indicates the number of methods, both static and dynamic, defined by this class. This table only includes those methods that are explicitly defined by this class. It does not include inherited methods.

methods table

Each value in the methods table <b>574</b> is a more complete description of a method in the class. Each method is described by a variable length method_info structure. The format of this structure is as follows:<img file="EP0834818A2_D0029.tif" />

The access_flags field is a set of sixteen flags used by classes, methods, and fields to describe various properties and how they many be accessed by methods in other classes. This field has the same names, values and meanings as the access_flags field <b>566</b> previously disclosed. The possible fields that can he set for a method are ACC_PUBLIC, ACC_PRIVATE, ACC_PROTECTED, ACC_STATIC ACC_FINAL, ACC_SYNCHRONIZED, ACC_NATIVE, and ACC_ABSTRACT. At most one of ACC_PUBLIC, ACC_PROTECTED, and ACC_PRIVATE can be set for any method.

The name_index field is a subscript used to index into the constant pool <b>565</b> indicating a CONSTANT_Utf8 string, which is the name of the method.

The signature_index field is a subscript that is used to index into the constant pool <b>565</b> to indicate a CONSTANT_Utf8 string, which is the signature of the method.

The attributes_countfield indicates the number of additional attributes about this method.

The attributes field represents the attributes of a particular method represented by the method_info structure. A method can have any number of optional attributes associated with it. Each attribute has a flame, and other additional information. For example, the "Code" attribute describes the bytecodes that are executed to perform this method, and the "Exceptions" attribute describes the Java Exceptions that are declared to result from the execution of the method.

attributes_count

The attributes_countfield <b>575</b> indicates the number of additional attributes about this class.

attributes

The attributes table <b>576</b> defines the attributes associated with the class. A class can have any number of optional attributes associated with it. For example, the <img file="EP0834818A2_D0030.tif" />SourceFile<img file="EP0834818A2_D0031.tif" /> attribute indicates the name of the source file from which this class file was compiled.

Because of the highly structured nature of the Java CLASS file format, the file format is particularly well-suited for the purpose of encoding an OID into an applet file. In particular, the OID may be encoded as a attribute associated with the applet class. The structured nature of the CLASS format facilitates retrieval of the OID attribute. The OID may be most easily implemented as an attribute associated with the class and encoded into attribute table <b>576</b>. It will be recalled that attribute table <b>576</b> includes all attributes associated with this class, such as the "SourceFile" attribute. An additional attribute, the OID attribute may be implemented to provide the OID for the applet.

The OID attribute has the following format:<img file="EP0834818A2_D0032.tif" />

The attribute_name_indexfield is a two-byte field that provides an index into constant pool <b>565</b>. The value in the attribute_name_indexfield is used to select a constant pool entry of type CONSTANT_Utf8 string encoding the character string "OID".

The attribute_lengthfield is a four-byte field containing the value 0x0002, indicating that the following oid_index field is two bytes in length.

The oid_indexfield is a two-byte field that that provides an index into constant pool <b>565</b>. The value in the oid_indexfield is used to select a constant pool entry of type CONSTANT_Utf8 string. The string encoded in the selected CONSTANT_Utf8 string is the ASN.1 OID value associated with this applet.

Another file type that lends itself to including an embedded OID is the CompuServe Information Service's Graphics Interchange Format (GIF). The GIF file format is described in CompuServe, Inc., <i>Graphics Interchange Format Version 89a (modified)</i> (January 9, 1995), the disclosure of which is hereby incorporated by reference. The GIF specification is primarily geared to the encoding of compressed data that may be used to represent a graphic image. The GIF format specifies the optional inclusion of an Application Extension, a data area that may include application-specific data, Figure 5B depicts the format of an Application Extension data area <b>580</b>.

One-byte Extension Introducer <b>581</b> has a value 0x21, which defines the data area as an extension. One-byte Application Extension Label <b>582</b> has a value 0xFF, which identifies the extension as an Application Extension. Blocksize <b>583</b> is a one-byte field that defines the size of the block, up to but not including Application Data <b>586</b>, and has the value 0x0B (decimal 11). Application Identifier <b>584</b> is an eight-byte printable ASCII sequence used to identify the application associated with the Application Extension. A value of 'ASN. 1OID' indicates that the Application Extension <b>580</b> is used to encode an ASN. 1 OID. Application Authorization Code <b>585</b> is three bytes in length, and is optionally used by an application to validate the Application Identifier <b>585</b>. It need not be employed in the present invention. Application data <b>586</b> is application-dependentdata, and may be used to encode an OID. Block Terminator <b>587</b> is a one-byte field containing a value 0x00, and is used to indicate the end of the Application Extension <b>580</b>.

Application data <b>586</b> may be used to encode an OID in the following form:<img file="EP0834818A2_D0033.tif" />

Where the length field is an integer that indicates the length of the OID, and the oid field is a character value of the OID associated with the GIF file.

In the preferred embodiment, following the extraction of the OID from the received file, client computer <b>210</b> must perform some verification of received object <b>510</b>, to validate that the received object <b>510</b> does, in fact, correspond to the OID specified and allocated by the software distributor that has responsibility for the OID. Typically, this may be performed by transmitting with the object <b>510</b> a digital signature associated with the file. Numerous methods of calculating digital signatures are known. According to one such methodology, a "message digest" is first calculated based upon the contents of the file to be digitally signed, in this case file <b>510</b>. A message digest is the fixed-length result when a variable length message or file is provided to a one-way hashing function. A message digest helps verify that a message has not been altered, because a message digest calculated on an altered message would not equal the message digest on the unaltered message. After the message digest is calculated, the digest is encrypted using a private key associated with the software distributor. A recipient of the message (e.g., file <b>510</b>) and the encrypted message digest for that message may validate the content of the message by first calculating its own version of the message digest, and then decrypting the received message digest using a public key maintained and widely distributed by the software distributor, and known to be valid and associated with that software distributor because it can be validated with a known registration authority. If the calculated message digest is equal to the decrypted received message digest, the message is known to be unaltered.

Message validation may be performed using any of a number of widely available public key cryptography methods. Examples of such methods include Private Communications Technology ("PCT") from Microsoft, Inc., Secure Hyper-Text Transport Protocol ("SHTTP") from Theresa Systems, Shen, Kerberos, Photuris, Pretty Good Privacy ("PGP") and Ipv6.

It should be noted that validation is a required step only in an untrusted environment, where the status of received objects is not known or is not trusted. In a trusted environment, in which the integrity of the object IDs and their associated resources are known to be valid, or where there is a high degree of confidence in the OID-resource coherency and the consequences of incoherence are minimal, the validation step may be ignored. For example, in a non-mission- critical environment in which all clients and all servers are under the control of the authority responsible for all of the OIDs, the validation of received objects might be ignored.

Figure <b>6</b> depicts transmission of a second HTML document <b>610</b> from a second HTTP server <b>615</b>, named SYSB, to client <b>210</b> over communications link <b>620</b>. Upon receipt of document <b>610</b>, client <b>210</b> updates cache <b>230</b> as previously described. That is, client <b>210</b> adds a new row <b>238-3</b> in which URI column <b>245</b> is set to the URI for file <b>610</b>, OID column <b>247</b> is set to null, and cache pointer column <b>249</b> is set to point to cache element <b>620</b>.

Figure <b>7</b> depicts an example of HTML document <b>610</b> illustrative of the present invention. As with previous document <b>225</b>, HTML document <b>610</b> comprises a number of HTML tags <b>710</b>, including applet tag <b>730</b>. Applet tag <b>730</b> comprises a CODE parameter <b>740</b>, a WIDTH parameter <b>742</b>, and a HEIGHT parameter <b>744</b>, and OID parameter <b>750</b>. It will be noted that the values for the CODE, WIDTH, and HEIGHT parameters in applet tag <b>730</b> are arbitrary and are not the same as those previously shown for Applet tag <b>330</b> in Figure <b>3</b>. However, it will be noted that the OID parameter <b>750</b> has a value of 1.1.999999.72.6.3, which is identical to the previously obtained object, as can be seen by reference to cache table row <b>238-2</b> in Figure <b>5</b>. Therefore, it will be seen that there are two different methods by which client <b>210</b> may obtain a copy of the desired object. It may issue a second HTTP request to server SYSB <b>615</b> using the URI, or it may retrieve the corresponding cache element <b>520</b> from the cache.

Figure <b>8</b> depicts the process by which client computer <b>210</b> obtains a copy of the desired object. Using the OID as specified in document <b>610</b>, client computer <b>210</b> traverses cache table <b>235</b>, searching for a matching OID value in column <b>247</b>. As can be seen from Figure <b>8</b>, a match is found in row <b>238-2</b>. Client computer <b>210</b> then references the corresponding cache pointer column <b>249</b> for row <b>238-2</b>, which points to cache element <b>520</b> within cache <b>230</b>. Client computer <b>210</b> then copies cache element <b>520</b> from cache <b>230</b> to its own memory as shown by arrow <b>840</b>. It will be noted that the copy loaded, as shown by object <b>810</b>, is equal to the contents previously downloaded as shown in Figure <b>5</b> from server SYSA, and is not freshly loaded from server SYSB <b>615</b>. That is, the cache copy was obtained without regard for the location from which it was originally obtained, or from the location specified in HTML document <b>610</b>.

Thus, Figures <b>2</b> through <b>8</b> depict a location-independent means of obtaining copies of resources, which would otherwise require redundant transmission of copies of resources identical to copies that had already been previously obtained. Although the examples shown depict retrieval of a data object in the form of a Java applet or a GIF file, the invention may also be applied to retrieval of any machine-readable resource, for example, a portion of a computer program such as a subroutine or other program segment, a text file, a sound file, or a data object that comprises a collection of multiple data objects.

Figure <b>9</b> is a flow chart depicting the overall operation of the invention. Execution begins in step <b>910</b>. In step <b>920</b>, the client computer determines what resource is desired to be obtained, e.g., by examining an applet tag in a previously downloaded HTML file. In step <b>925</b>, the client computer checks to see whether an OID was specified for the desired resource. If no OID was specified, execution proceeds with step <b>930</b>. In step <b>930</b>, the client computer obtains a copy using the URI, for example by issuing an HTTP GET request to the server corresponding to the URI.

In step <b>935,</b> the client verifies that an OID was encoded into the retrieved copy. If so, control proceeds to step <b>940</b>. In step <b>940</b>, the client checks to see whether the OID is valid, for example, by verifying a digital signature. If so, control proceeds to step <b>950</b>. In step <b>950</b>, client computer <b>210</b> updates the OID status in the cache for the file obtained. If either no OID is specified in the retrieved copy, or an OID is specified but is not valid, step <b>950</b> is skipped, and control proceeds to step <b>990</b> where processing of the retrieved object is complete. As noted previously, the steps of verifying the OID from the copy of the retrieved object, and validating the OID against the received object, are optional and may be omitted in certain environments.

Referring again to step <b>925</b>, if an OID was specified, control proceeds to step <b>970</b>. In step <b>970</b>, the client computer inspects the cache table to determine whether an object with the desired object identifier has previously been downloaded and is available in the cache. If no such object is found in the cache, control proceeds to step <b>930</b>, as if no OID had been specified. If the desired OID entry is found in the cache table, however, control proceeds to step <b>975</b>, in which the client computer retrieves the cache copy, loads it into memory and proceeds to execute using the copy retrieved from the cache. In any event, after step <b>975</b>, processing for the object exits at step <b>990</b>.

Figure <b>10</b> depicts an alternate embodiment of the present invention. As shown in Figure <b>10</b>, a plurality of clients <b>1010</b> and <b>1020</b> are in communication with a firewall server <b>1040</b> using communication links <b>1030</b>. Firewall server <b>1040</b> may be, for example, a proxy server, a firewall or a gateway. Cache <b>1050</b> is operated under the control of firewall server <b>1040</b>. In response to request from clients <b>1010</b> and <b>1020</b>, firewall server <b>1040</b> makes requests to various servers in network <b>1060</b> over communication link <b>1070</b>.

In the embodiment depicted it is not necessary for clients <b>1010</b> and <b>1020</b> to maintain their own caches. Instead, requests for resources are provided to the firewall server <b>1040</b> and include both the location-dependent URI associated with the specific copy of the resource, as well as the location independent OID (if any) associated with the resource. Firewall server <b>1040</b> maintains cache <b>1050</b> as previously described. When an object with an OID corresponding to an OID requested by one of clients <b>1010</b> or <b>1020</b> is found in cache <b>1050</b>, firewall server <b>1040</b> responds to the respective client with a copy of the object as obtained from the cache. If no such object is found in the cache, firewall server <b>1040</b> uses the supplied URI to obtain a new copy from network <b>1060</b>.

While the invention is described in terms of preferred embodiments in a specific system environment, those skilled in the art will recognize that the invention can be practiced, with modification, in other and different hardware and software environments within the spirit and scope of the appended claims.