Source: http://www.google.com/patents/US6243716?dq=5,966,702
Timestamp: 2016-06-29 09:16:42
Document Index: 443611352

Matched Legal Cases: ['art 2', 'art 2', 'art 1', 'art 2', 'art 1', 'art 2']

Patent US6243716 - Methods and systems for distributed failure detection and recovery using leasing - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsA system for using a lease to detect a failure and to perform failure recovery is provided. In using this system, a client requests a lease from a server to utilize a resource managed by the server for a period of time. Responsive to the request, the server grants the lease, and the client continually...http://www.google.com/patents/US6243716?utm_source=gb-gplus-sharePatent US6243716 - Methods and systems for distributed failure detection and recovery using leasingAdvanced Patent SearchPublication numberUS6243716 B1Publication typeGrantApplication numberUS 09/377,491Publication dateJun 5, 2001Filing dateAug 20, 1999Priority dateOct 11, 1996Fee statusPaidAlso published asEP0836140A2, EP0836140A3, US5832529, US6016500, US6263350, US6314435, US6327596, US6519615, US6704756, US6760736, US6816875, US7509360, US20010000812, US20020002576, US20030208512, US20050004914Publication number09377491, 377491, US 6243716 B1, US 6243716B1, US-B1-6243716, US6243716 B1, US6243716B1InventorsJames H. Waldo, Ann M. Wollrath, Robert Scheifler, Kenneth C. R. C. ArnoldOriginal AssigneeSun Microsystems, Inc.Export CitationBiBTeX, EndNote, RefManPatent Citations (129), Non-Patent Citations (101), Referenced by (64), Classifications (56), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetMethods and systems for distributed failure detection and recovery using leasing
US 6243716 B1Abstract
A system for using a lease to detect a failure and to perform failure recovery is provided. In using this system, a client requests a lease from a server to utilize a resource managed by the server for a period of time. Responsive to the request, the server grants the lease, and the client continually requests renewal of the lease. If the client fails to renew the lease, the server detects that an error has occurred to the client. Similarly, if the server fails to respond to a renew request, the client detects that an error has occurred to the server. As part of the lease establishment, the client and server exchange failure-recovery routines that each invokes if the other experiences a failure.
What is claimed is: 1. A method for recovering from failures in a distributed system that includes a client and a server, said method comprising the steps of:
requesting by the client a lease from the server for using a resource managed by the server; granting the lease by the server to the client for a period of time; and detecting by the client a first failure when a request to renew the granted lease fails. 2. The method of claim 1, further comprising the steps of:
detecting by the server a second failure when the granted lease expires. 3. The method of claim 2, further comprising the step of:
recovering the client by rolling back the client and the resource to a prenegotiated state. 4. The method of claim 3, wherein the recovering step includes the step of:
invoking a method provided by the client to the server for recovering the client and the resource. 5. The method of claim 1, further comprising the step of:
recovering the server by rolling back the server and the resource to a prenegotiated state. 6. The method of claim 5, wherein the recovering step includes the step of:
invoking a method provided by the server to the client for recovering the server and the resource. 7. The method of claim 1, wherein the requesting step includes the step of:
sending to the server a request that includes a resource identifier and the period of time. 8. The method of claim 1, wherein the requesting step includes the step of:
sending to the server a request that includes a type of access to the resource requested by the client. 9. The method of claim 1, wherein the requesting step includes the step of:
sending to the server a request that includes a privilege level associated with the client. 10. The method of claim 1, wherein the requesting step includes the step of:
sending to the server an object that includes a method for recovering the client. 11. The method of claim 1, wherein the granting step includes the step of:
sending to the client an object that includes a method for recovering the server. 12. The method of claim 1, wherein the granting step includes the step of:
sending to the client an object that includes a method for renewing the lease. 13. The method of claim 1, wherein the granting step includes the step of:
sending to the client an object that includes a method for canceling the lease. 14. The method of claim 1, wherein the granting step includes the step of:
sending to the client an object that includes a method for determining the period of time of the lease. 15. A data processing system, comprising:
a memory including: a client program containing a first code that requests a lease for using a resource and containing second code that detects a first failure when a request by the client program to extend the lease fails; and a server program containing third code that manages the resource, containing fourth code that grants the lease to the client program for a period of time, and containing fifth code that detects a second failure when the lease expires; and a processor for running the client program and the server program. 16. The data processing system of claim 15, wherein the client program includes sixth code that recovers the server program by rolling back the server program and the resource to a prenegotiated state when the client program detects the first failure.
17. The data processing system of claim 15, wherein the server program includes seventh code that recovers the client program by rolling back the client program and the resource to a prenegotiated state when the server program detects the second failure.
a storage device including a first object generated by the client program when requesting the lease from the server program. 19. The data processing system of claim 18, wherein the first object includes a method for recovering the client program by the server program.
a storage device including a second object generated by the server program when granting the lease to the client program. 21. The data processing system of claim 20, wherein the second object includes a method for recovering the server program by the client program.
22. The data processing system of claim 20, wherein the second object includes a method for extending the lease by the client program.
23. The data processing system of claim 20, wherein the second object includes a method for canceling the lease by the client program.
24. A computer-readable medium containing instructions for controlling a data processing system to perform a method, the data processing system including a client and a server, said method comprising the steps of:
requesting by the client a lease from the server for using a resource managed by the server; generating by the server a lease object that grants the lease to the client; detecting by the client a first failure when a request by the client to renew the lease fails; and detecting by the server a second failure when the granted lease expires before receiving from the client a request to cancel the lease. 25. The computer-readable medium of claim 24, wherein said method further comprises the step of:
recovering the server by invoking a recovery routine in the lease object by the client. 26. The computer-readable medium of claim 25, wherein said recovering step includes the step of:
recovering the server by rolling back the server and the resource by the client to a prenegotiated state. 27. The computer-readable medium of claim 24, wherein said method further comprises the step of:
recovering the client by invoking a recovery routine provided to the server by the client when the client requested the lease. 28. The computer-readable medium of claim 27, wherein said recovering step includes the step of:
recovering the client by rolling back the client and the resource by the server to a prenegotiated state. 29. An apparatus for recovering from failures in a distributed system, comprising:
a requesting means for requesting a lease for using a resource and for detecting a first failure when a request by the requesting means to renew the lease fails; and a resource allocating means for granting the lease to the client program for a period of time and for detecting a second failure when the lease expires before receiving from the requesting means a request to cancel the lease. 30. A method for recovering from failures in a distributed system that includes a client and a server, said method comprising the steps of:
requesting by the client a lease from the server for using a resource managed by the server for a period of time; receiving by the client from the server a first object that grants the lease to the client and includes a method for recovering the server; sending by the client to the server a request to renew the granted lease; and detecting by the client a first failure when the request to renew the granted lease fails. 31. The method of claim 30, further comprising the step of:
recovering the server by invoking the recovery method in the first object by the client. 32. The method of claim 30, wherein the requesting step comprises the step of:
sending to the server a second object that includes a recovery method for recovering the client when the server detects that the lease has expired before receiving from the client a request to cancel the lease. 33. A method for recovering from failures in a distributed system including a client and a server, said method comprising the steps of:
receiving by the server a request from the client for a lease for using a resource managed by the server; granting the lease to the client for a period of time by sending to the client a first object that includes a method for recovering the server; and detecting by the server a failure when the granted lease expires. 34. The method of claim 33, wherein the receiving step includes the step of:
receiving a second object that includes a method for recovering the client by the server. 35. The method of claim 33, wherein the detecting step includes the step of:
detecting by the server a failure when the granted lease expires before receiving from the client a request to cancel the granted lease. 36. The method of claim 33, wherein the detecting step includes the step of:
detecting by the server a failure when the granted lease expires before receiving from the client a request to renew the granted lease. 37. A computer-readable memory device encoded with a data structure for recovering from failures in a distributed system including a client and a server, the data structure comprising:
an object including an identifier identifying a resource leased by the client from the server and a recovery method for recovering the server and the resource by the client when a request by the client to renew the lease fails. 38. The computer-readable memory device of claim 37, further comprising:
a renewing method for renewing the granted lease when the client determines that the lease is near expiration. 39. The computer-readable memory device of claim 37, further comprising:
a canceling method for canceling the granted lease when the client completes use of the resource. 40. The computer-readable memory device of claim 37, further comprising:
a duration method for determining the period of time of the granted lease. 41. A computer-readable memory device encoded with a data structure for recovering from failures in a distributed system including a client and a server, the data structure comprising:
an identifier identifying a resource leased by the client from the server for a period of time; and an object including a recovery method for recovering the client and the resource by the server when the lease expires. 42. The computer-readable memory device of claim 41, wherein the recovery method recovers the client and the resource when the lease expires before the server receives a request from the client to cancel the lease.
43. The computer-readable memory device of claim 41, wherein the recovery method recovers the client and the resource when the lease expires before the server receives a request from the client to renew the lease.
44. The computer-readable memory device of claim 43, further comprising:
a type of access to the resource requested by the client. 45. The computer-readable memory device of claim 43, further comprising:
a privilege level associated with the client. 46. A method for recovering from failures in a distributed system that includes a client and a server, said method comprising the steps of:
exchanging code between the client and the server during a lease negotiation for using a resource managed by the server; and invoking the code to perform system management. 47. The method of claim 46, wherein the invoking step includes the step of:
recovering the client by the server when the server detects a failure. 48. The method of claim 46, wherein the invoking step includes the step of:
recovering the client and the resource by the server when the server detects a failure. 49. The method of claim 46, wherein the invoking step includes the step of:
recovering the server by the client when the client detects a failure. 50. The method of claim 46, wherein the invoking step includes the step of:
recovering the server and the resource by the client when the client detects a failure.
This is a divisional of application Ser. No. 09/044,916, filed Mar. 20, 1998, now U.S. Pat. No. 6,016,500, which was a Continuation-in-Part of Ser. No. 08/729,421, filed Oct. 11, 1996, now U.S. Pat. No. 5,832,529.
U.S. patent application Ser. No. 09/044,933, entitled “Method for Transporting Behavior in Event Based System,” filed on the same date herewith.
U.S. patent application Ser. No. 09/044,939, entitled “Apparatus and Method for Providing Downloadable Code for Use in Communicating with a Device in a Distributed System,” on the same date herewith.
Referential integrity failures and memory leaks often result from disconnections between applications referencing the resources and the garbage collection system managing the allocation and deallocation of those resources. For example, a disconnection in a network connection between an application referring to a resource and a garbage collection system managing that resource may prevent the garbage collection system from determining whether and when to reclaim the resource. Alternatively, the garbage collection system might mistakenly determine that, since an application has not accessed a resource within a predetermined time, it may collect that resource. A number of techniques have been used to improve the distributed garbage collection mechanism by attempting to ensure that such mechanisms maintain referential integrity without memory leaks. One conventional approach uses a form of reference counting, in which a count is maintained of the number of applications referring to each resource. When a resource's count goes to zero, the garbage collection system may reclaim the resource. Such a reference counting scheme only works, however, if the resource is created with a corresponding reference counter. The garbage collection system in this case increments the resource's reference count as additional applications refer to the resource and decrements the count when an application no longer refers to the resource.
In addition to failure detection, the alternative embodiment also provides for failure recovery. During the establishment of the lease, the client provides the server with a failure recovery routine, and likewise, the server provides the client with a failure recovery routine. Thus, upon detection of a failure, both the client and the server each invoke the failure recovery routine of the other to perform failure recovery for each other. After performing failure recovery, both the client and the server then go to a prenegotiated state. That is, the client and the server, through a negotiation beforehand, have decided upon a state that they will go to upon experiencing an error, such as rolling back all changes made to the resource. As a result, both the client and the server know the state of the system after a failure and can continue processing accordingly.
In general, whenever an application in the distributed processing system obtains a reference to a distributed resource, by a name lookup, as a return value to some other call, or another method and seeks to access the resource, the application makes a call to the resource or to an MI component managing the resource. That MI component, called a managing MI component, keeps track of the number of outstanding references to the resource. When the number of references to a resource is zero, the managing MI component can reclaim the resource. The count of the number of references to a resource is generally called the “reference count” and the call that increments the reference count may be referred to as a “dirty call.”
If the application is not yet done with the reference (step 130), but the application call processor determines that the grant period for the reference is about to expire (step 160), then the application call processor repeats steps 10 and 120 to ensure that the reference to the resource is maintained by the managing MI component on behalf of the application.
The MI component's server call processor also handles incoming clean calls from application call processors. When an application in the distributed processing system no longer requires a reference to a resource, it informs the MI component managing the resource for that reference, so that the resource may be reclaimed for reuse. FIG. 3 is a flow diagram of the procedure 300 with the steps that the MI component's server call processor uses to handle clean calls.
Both applications 510 and 540 may request access to the same resource. For example, application 510 may request access to “RESOURCE(1)” while application 540 was previously granted access to that resource. MI component 525 handles this situation by making the resource available to both applications 510 and 540 for agreed lease periods. Thus, MI component 525 will not initiate a garbage collection cycle to reclaim the “RESOURCE(1)” until either applications 510 and 540 have both dropped their references to that resource or the latest agreed periods has expired. whichever event occurs first.
In the implementation of distributed processing system 50, platforms 700, 800 and 900 each include a processor 710, 810, and 910 respectively, and a memory, 750, 850, and 950, respectively. Included within each processor 710, 810, and 910, are applications 720, 820, and 920, respectively, operating systems 740, 840, and 940, respectively, and MI components 730, 830, and 930. respectively.
Platforms 1000 and 1100 contain memories 1050 and 1150, respectively, and processors 1010 and 1110, respectively. The elements in the platforms 1000 and 1100 function in the same manner as similar elements described above with reference to FIG. 7. In this example. processor 1010 executes a client application 1020 and processor 1110 executes a server application 1120. Processors 1010 and 1110 also execute operating systems 1040 and 1140, respectively, and MI components 1030 and 1130, respectively.
Upon detecting a failure, the client and the server perform a recovery by proceeding to a prenegotiated state. That is, the client and the server prenegotiate a state that they will go to upon experiencing or detecting a failure. For instance, in the above file system example, the client and server may prenegotiate to perform a roll back if a failure is detected. A “roll back” refers to putting the client, server, and any related entities, such as the file, in the state they were in before the failure occurred. Thus, in the example, if the server had already performed the write operation, the server restores the file to its state just before the write operation was performed and the client knows that. after the failure is detected, the write operation has not been performed, so the client can continue its processing accordingly.
Alternatively, the client and server may roll back even further. For example, the client and server may prenegotiate that whenever an error occurs during file manipulation, the roll back brings the client and server back to the state they were in before the client had the lease (e.g., before the file was created). Another alternative is that the roll back may instead go back to a predetermined checkpoint in the manipulation of the file. This prenegotiation between the client and server to determine the after-failure system state can be performed in a number of ways, including a handshake, reading a predesignated file, or the client and server may simply be instructed at development time to always go to a given after-failure system state.
The alternative embodiment can be used in any client-server relationship, including operation in a distributed system where the client and server are located on separate machines communicating via a network or where the client and server are on the same machine. Such a distributed system suitable for use by the alternative embodiment is the exemplary distributed system described in copending U.S. patent application Ser. No. 09/044,931, entitled “Dynamic Lookup Service in a Distributed System,” which has been previously incorporated by reference. For purposes of clarity, however, the alternative embodiment will be described below with respect to the server being a file system manager that leases storage locations on a secondary storage device.
Overview of Leasing Storage Locations
Storage devices have many storage locations containing various logical groupings of data that may be used by more than one program. These logical groupings may take the form of files databases, or documents. The leasing of storage locations allows access (e.g., read and write access) to the storage locations for a pre-negotiated amount of time. It is immaterial to the leasing of storage locations what kind of data is contained in the storage locations or whether the storage locations contain any data at all. Also, the leasing of storage locations can be applied on different levels of storage, such as database fields, files, blocks of storage, or actual storage locations.
When using a lease for a group of storage locations containing the data for a file, a program (“the client”) requests a lease from the file system manager (“the server”) to access the group of storage locations for a period of time (“the lease period”). Depending on availability, priority, and other factors, the server either denies the request or grants a lease period. The lease period granted may be either the entire lease period requested or some portion of it. Once a client receives a lease, the client may access the group of storage locations for the duration of the lease period.
While a lease is active, the client is guaranteed access to the group of storage locations and may perform read and write operations on them. And, likewise, the server, during an active lease will maintain the storage locations' integrity. For example, during the lease period, the server will not allow the leased file to be deleted, written over, or otherwise corrupted by any entity other than the client, unless that entity also has a lease. After a lease expires, however, the server no longer guarantees the integrity of the file to the client, and thus, the server may delete the file or otherwise materially change it, or grant a lease to another client that may do the same. Storage locations with no outstanding leases are reclaimed by the server.
The alternative embodiment also supports concurrent access to a group of storage locations by granting multiple, concurrent leases to the same storage locations. For example. if a particular group of storage locations' parameter specifies “read” access, the server can grant multiple concurrent leases to that storage location without breaching the integrity of the storage location. Concurrent leases could also be applied, for example, to large files. The server could merely grant leases to smaller sub-blocks of the file without compromising the integrity of the larger file.
public void cancel ( ) throws
This class contains a number of methods, including the getDuration method, the cancel method, the renew method, and the recover method. The “getDuration” method provides the client with the length of the granted lease period. This period represents the most recent lease granted by the server. It is the client's responsibility however, to determine the amount of time remaining on the lease.
The client may use the renew method to request an additional lease period, or the client may continually invoke the renew method multiple times until many additional lease periods are granted. The renew method has no return value. If the renewal is granted, the new lease period will be reflected in the lease object on which the call was made. If the server is unable or unwilling to renew the lease, the reason is set forth in the lease object on which the call was made.
The leasing of storage locations is described in greater detail in co-pending U.S. patent application Ser. No. 09/044,923, entitled “Method and System for Leasing Storage” which has previously been incorporated by reference.
The Java space 9019 is an object repository used by programs within the data processing system 9000 to store objects. Programs use the Java space 9019 to store objects persistently as well as to make them accessible to other devices on the network. Java spaces are described in greater detail in co-pending U.S. patent application Ser. No. 08/971,529, entitled “Database System Employing Polymorphic Entry and Entry Matching,” assigned to a common assignee, filed on Nov. 17, 1997, which is incorporated herein by reference. One skilled in the art will appreciate that computer 9000 may contain additional or different components.
FIG. 10 depicts a flowchart of the steps performed by the client when requesting a lease from the server. The first step performed by the client is to send a request for a lease to the server (step 10002). This request is a function call with a number of parameters, including (1) the requested storage locations the client wishes to lease, (2) the desired lease period, (3) an exact lease indicator, (4) the type of access the client desires, (5) the client's privilege, and (6) an object containing a recover method. This method contains code for performing error recovery for the client.
After sending the request, the client receives a lease object from the server (step 10004). The lease object contains various information, as described above, including the file handle, the getDuration method, the renew method, the cancel method, and the recover method.
FIG. 11 depicts a flowchart of the steps performed by the server in accordance with an alternative embodiment of the present invention. The first step performed by the server is to access the Java space 9019 (step 11002). The server maintains a Java space in which it stores all objects received during a lease request. These objects are stored in the Java space so that if the server detects a failure, it may access the Java space and perform recovery by invoking the recover methods on the objects. Furthermore, the objects are stored persistently so if the server experiences a failure and crashes, when the server is restarted, it may invoke the recover method on each object in the Java space, reflecting all of the outstanding leases at the time of the server failure. In step 11002, the server accesses the Java space containing all objects, if any, received from clients as part of lease requests. If there are any objects in the Java space, a failure must have occurred during the processing of the server.
After storing the object in the Java space, the server grants the lease request by returning an object with the methods described above, including a recover method for the server (step 11012). At some point later in the processing of the server, the server determines whether it has received a renew request from the client (step 11014). If the renew request has been received the server renews the lease (step 11017). If, however, a renew has not been received, the server determines if a cancel request has been received by the client invoking the cancel method (step 11015). If the client invoked the cancel method, the server cancels the lease by deleting the object stored in step 11010 from the Java space, and if this is the last outstanding lease on the file, the server deletes the file (step 11016).
If a cancel request was not received, the server determines if the lease has expired (step 11018). If the lease has not expired, processing continues to step 11014. However, if the lease has expired, the server knows that a failure has occurred and therefore invokes the recover method on the object in the Java space for the client with the lease that terminated (step 11020). After invoking the recover method the server deletes this object because it is no longer needed (step 11022).
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS4491946Mar 9, 1981Jan 1, 1985Gould Inc.Multi-station token pass communication systemUS4713806Mar 14, 1986Dec 15, 1987American Telephone And Telegraph Company, At&T Bell LaboratoriesCommunication system control arrangementUS4809160Oct 28, 1985Feb 28, 1989Hewlett-Packard CompanyPrivilege level checking instruction for implementing a secure hierarchical computer systemUS4823122Aug 24, 1987Apr 18, 1989Digital Equipment CorporationLocal area network for digital data processing systemUS4939638Feb 23, 1988Jul 3, 1990Stellar Computer Inc.Time sliced vector processingUS4956773Mar 28, 1989Sep 11, 1990Hitachi, Ltd.System and method of generating a source program from inputted schematic informationUS5088036Jan 17, 1989Feb 11, 1992Digital Equipment CorporationReal time, concurrent garbage collection system and methodUS5109486Jan 6, 1989Apr 28, 1992Motorola, Inc.Distributed computer system with network and resource status monitoringUS5187787Jul 27, 1989Feb 16, 1993Teknekron Software Systems, Inc.Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processesUS5218699Jun 8, 1992Jun 8, 1993International Business Machines CorporationRemote procedure calls in heterogeneous systemsUS5257369Oct 22, 1990Oct 26, 1993Skeen Marion DApparatus and method for providing decoupling of data exchange details for providing high performance communication between software processesUS5293614Apr 8, 1991Mar 8, 1994Texas Instruments IncorporatedSystem and method for hard real-time garbage collection requiring a write barrier but no read barrierUS5297283Oct 16, 1992Mar 22, 1994Digital Equipment CorporationObject transferring system and method in an object based computer operating systemUS5311591Jun 3, 1993May 10, 1994Fischer Addison MComputer system security method and apparatus for creating and using program authorization information data structuresUS5386568Dec 1, 1992Jan 31, 1995Yamaha CorporationApparatus and method for linking software modulesUS5390328Mar 30, 1992Feb 14, 1995International Business Machines CorporationData processing system and method for providing notification in a central processor of state changes for shared data structure on external storageUS5399435Jan 16, 1992Mar 21, 1995Asahi Glass Company Ltd.Amorphous oxide film and article having such film thereonUS5423042Oct 23, 1992Jun 6, 1995International Business Machines CorporationRemote procedure executionUS5440744Nov 15, 1994Aug 8, 1995Digital Equipment CorporationMethods and apparatus for implementing server functions in a distributed heterogeneous environmentUS5448740Oct 1, 1993Sep 5, 1995International Business Machines CorporationGeneration of a user interface code from a corresponding declarative language programUS5452459Jan 8, 1993Sep 19, 1995Digital Equipment CorporationMethod and apparatus for allocating server access in a distributed computing environmentUS5455952Mar 28, 1995Oct 3, 1995Cardinal Vision, Inc.Method of computing based on networks of dependent objectsUS5471629Jul 20, 1992Nov 28, 1995Hewlett-Packard CompanyMethod of monitoring changes in an object-oriented database with tuned monitorsUS5475792Feb 24, 1994Dec 12, 1995International Business Machines CorporationTelephony channel simulator for speech recognition applicationUS5475817Nov 30, 1993Dec 12, 1995Hewlett-Packard CompanyObject oriented distributed computing system processing request to other object model with code mapping by object managers located by manager of object managersUS5481721Oct 31, 1994Jan 2, 1996Next Computer, Inc.Method for providing automatic and dynamic translation of object oriented programming language-based message passing into operation system message passing using proxy objectsUS5504921May 16, 1994Apr 2, 1996Cabletron Systems, Inc.Network management system using model-based intelligenceUS5511197Nov 29, 1993Apr 23, 1996Microsoft CorporationMethod and system for network marshalling of interface pointers for remote procedure callsUS5524244Feb 15, 1994Jun 4, 1996Logic Devices, Inc.System for dividing processing tasks into signal processor and decision-making microprocessor interfacing therewithUS5553282Dec 9, 1994Sep 3, 1996Taligent, Inc.Software project history database and method of operationUS5555367Sep 30, 1994Sep 10, 1996General Electric CompanyMethod and system for generating computer programs for queries formed by manipulating object-oriented diagramsUS5557798Dec 21, 1990Sep 17, 1996Tibco, Inc.Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processesUS5560003Dec 21, 1992Sep 24, 1996Iowa State University Research Foundation, Inc.System and hardware module for incremental real time garbage collection and memory managementUS5561785Oct 29, 1992Oct 1, 1996International Business Machines CorporationSystem for allocating and returning storage and collecting garbage using subpool of available blocksUS5577231Dec 6, 1994Nov 19, 1996International Business Machines CorporationStorage access authorization controls in a computer system using dynamic translation of large addressesUS5603031Jul 8, 1993Feb 11, 1997General Magic, Inc.System and method for distributed computation based upon the movement, execution, and interaction of processes in a networkUS5617537Oct 3, 1994Apr 1, 1997Nippon Telegraph And Telephone CorporationMessage passing system for distributed shared memory multiprocessor system and message passing method using the sameUS5628005Jun 7, 1995May 6, 1997Microsoft CorporationSystem and method for providing opportunistic file access in a network environmentUS5640564Jun 6, 1995Jun 17, 1997Sun Microsystems, Inc.Method and apparatus for generating and using short operation identifiers in object oriented systemsUS5644768Dec 9, 1994Jul 1, 1997Borland International, Inc.Systems and methods for sharing resources in a multi-user environmentUS5652888Jun 7, 1995Jul 29, 1997Microsoft CorporationSystem for interconnecting software components in an object oriented programming environment using a separate editor object for each run-time object instantiated for each selected componentUS5655148Dec 13, 1994Aug 5, 1997Microsoft CorporationMethod for automatically configuring devices including a network adapter without manual intervention and without prior configuration informationUS5659751Dec 3, 1992Aug 19, 1997Apple Computer, Inc.Apparatus and method for dynamic linking of computer software componentsUS5671225Sep 1, 1995Sep 23, 1997Digital Equipment CorporationDistributed interactive multimedia service systemUS5675796Aug 16, 1996Oct 7, 1997Microsoft CorporationConcurrency management component for use by a computer program during the transfer of a messageUS5680573Jul 12, 1994Oct 21, 1997Sybase, Inc.Method of buffering data objects in a databaseUS5680617May 16, 1994Oct 21, 1997Apple Computer, Inc.Computer-human interface which provides for user customization of object behaviorUS5684955Jun 30, 1992Nov 4, 1997Siemens AktiengesellschaftProcess for distributing an object-oriented program over a plurality of operating system processes of a computer systemUS5689709Feb 1, 1996Nov 18, 1997Microsoft CorporationMethod and system for invoking methods of an objectUS5706435Jul 26, 1996Jan 6, 1998Panasonic Technologies, Inc.System for maintaining data coherency in cache memory by periodically broadcasting a single invalidation report from server to clientsUS5724588Jun 7, 1995Mar 3, 1998Microsoft CorporationMethod and system for network marshalling of interface pointers for remote procedure callsUS5727145Jun 26, 1996Mar 10, 1998Sun Microsystems, Inc.Mechanism for locating objects in a secure fashionUS5737607Sep 28, 1995Apr 7, 1998Sun Microsystems, Inc.Method and apparatus for allowing generic stubs to marshal and unmarshal data in object reference specific data formatsUS5745678Aug 18, 1997Apr 28, 1998International Business Machines CorporationMethod and system for the secured distribution of multimedia titlesUS5745703Jul 18, 1995Apr 28, 1998Nec Research Institute, Inc.Transmission of higher-order objects across a network of heterogeneous machinesUS5754849Jan 30, 1996May 19, 1998Wayfarer Communications, Inc.Self-describing object providing dynamic manipulation of heterogeneous data values and semantic identity between memory and transmission representationsUS5757925Jul 23, 1996May 26, 1998Faybishenko; YaroslavSecure platform independent cross-platform remote execution computer system and methodUS5761656Jun 26, 1995Jun 2, 1998Netdynamics, Inc.Interaction between databases and graphical user interfacesUS5764897Oct 28, 1996Jun 9, 1998Sun Microsystems, Inc.Method and apparatus for managing transactions in an object-oriented distributed systemUS5768532Jun 17, 1996Jun 16, 1998International Business Machines CorporationMethod and distributed database file system for implementing self-describing distributed file objectsUS5774551Aug 7, 1995Jun 30, 1998Sun Microsystems, Inc.Pluggable account management interface with unified login and logout and multiple user authentication servicesUS5778228Aug 16, 1994Jul 7, 1998International Business Machines CorporationMethod and system for transferring remote procedure calls and responses over a networkUS5778368May 3, 1996Jul 7, 1998Telogy Networks, Inc.Real-time embedded software respository with attribute searching apparatus and methodUS5787425Oct 1, 1996Jul 28, 1998International Business Machines CorporationObject-oriented data mining framework mechanismUS5787431Dec 16, 1996Jul 28, 1998Borland International, Inc.Database development system with methods for java-string reference lookups of column namesUS5790548Apr 18, 1996Aug 4, 1998Bell Atlantic Network Services, Inc.Universal access multimedia data networkUS5809507Jul 1, 1996Sep 15, 1998Sun Microsystems, Inc.Method and apparatus for storing persistent objects on a distributed object network using a marshaling frameworkUS5812819 *Jun 5, 1995Sep 22, 1998Shiva CorporationRemote access apparatus and method which allow dynamic internet protocol (IP) address managementUS5813013Jun 6, 1996Sep 22, 1998Microsoft CorporationRepresenting recurring eventsUS5815149Feb 19, 1997Sep 29, 1998Unisys Corp.Method for generating code for modifying existing event routines for controls on a formUS5815709Apr 23, 1996Sep 29, 1998San Microsystems, Inc.System and method for generating identifiers for uniquely identifying object types for objects used in processing of object-oriented programs and the likeUS5815711Nov 6, 1995Sep 29, 1998Hitachi, Ltd.Apparatus and method for program generationUS5829022Apr 15, 1996Oct 27, 1998Fuji Xerox Co., Ltd.Method and apparatus for managing coherency in object and page cachesUS5832529Oct 11, 1996Nov 3, 1998Sun Microsystems, Inc.Methods, apparatus, and product for distributed garbage collectionUS5835737May 10, 1996Nov 10, 1998Apple Computer, Inc.Method and apparatus for arbitrating access to selected computer system devicesUS5842018Jun 6, 1995Nov 24, 1998Microsoft CorporationMethod and system for referring to and binding to objects using identifier objectsUS5844553Mar 29, 1996Dec 1, 1998Hewlett-Packard CompanyMechanism to control and use window events among applications in concurrent computingUS5845129Mar 22, 1996Dec 1, 1998Philips Electronics North America CorporationProtection domains in a single address spaceUS5860004Jul 3, 1996Jan 12, 1999Sun Microsystems, Inc.Code generator for applications in distributed object systemsUS5860153Nov 22, 1995Jan 12, 1999Sun Microsystems, Inc.Memory efficient directory coherency maintenanceUS5864862Sep 30, 1996Jan 26, 1999Telefonaktiebolaget Lm Ericsson (Publ)System and method for creating reusable components in an object-oriented programming environmentUS5864866Mar 26, 1997Jan 26, 1999International Business Machines CorporationApparatus and method for providing externalization in an object-oriented environmentUS5872928May 25, 1995Feb 16, 1999Cabletron Systems, Inc.Method and apparatus for defining and enforcing policies for configuration management in communications networksUS5875335Sep 30, 1996Feb 23, 1999Apple Computer, Inc.Parameter marshaling techniques for dynamic object-oriented programming languagesUS5878411Jun 27, 1997Mar 2, 1999International Business Machines CorporationDependent object class and subclass mapping to relational data storeUS5884024 *Dec 9, 1996Mar 16, 1999Sun Microsystems, Inc.Secure DHCP serverUS5884079Jun 12, 1997Mar 16, 1999Yamatake-Honeywell Co., Ltd.Design part reusing method in configuration toolUS5887134Jun 30, 1997Mar 23, 1999Sun MicrosystemsSystem and method for preserving message order while employing both programmed I/O and DMA operationsUS5889951 *May 13, 1996Mar 30, 1999Viewpoint CorporationSystems, methods, and computer program products for accessing, leasing, relocating, constructing and modifying internet sites within a multi-dimensional virtual reality environmentUS5890158Mar 31, 1997Mar 30, 1999International Business Machines CorporationMethod, apparatus, and program storage device for sharing objects with a network server and a database server using a common object modelUS5892904Dec 6, 1996Apr 6, 1999Microsoft CorporationCode certification for network transmissionUS5933497Jan 29, 1993Aug 3, 1999International Business Machines CorporationApparatus and method for controlling access to softwareUS5935249Feb 26, 1997Aug 10, 1999Sun Microsystems, Inc.Mechanism for embedding network based control systems in a local network interface deviceUS5940827Nov 10, 1997Aug 17, 1999Sun Microsystems, Inc.Methods and apparatus for managing a database in a distributed operating environmentUS5946485Feb 9, 1996Aug 31, 1999Intervoice Limited PartnershipEnhanced graphical development environment for controlling program flowUS5946694Sep 29, 1997Aug 31, 1999International Business Machines CorporationApparatus and method for transparent application of service to business objectsUS5966531Jun 7, 1995Oct 12, 1999Reuters, Ltd.Apparatus and method for providing decoupled data communications between software processesUS6003763Dec 29, 1995Dec 21, 1999Visa International ServiceMethod and apparatus for recording magnetic information on traveler's checksUS6009103Dec 23, 1997Dec 28, 1999Mediaone Group, Inc.Method and system for automatic allocation of resources in a networkUS6061699Nov 3, 1997May 9, 2000International Business Machines CorporationMethod and computer program product for extracting translatable material from browser program function codes using variables for displaying MRIUS6061713Mar 12, 1997May 9, 2000Fujitsu LimitedCommunications system for client-server data processing systemsEP0300516A2May 21, 1982Jan 25, 1989Data General CorporationDigital data processing systemEP0351536A2Jun 8, 1989Jan 24, 1990International Business Machines CorporationSystematic recovery of excessive spin loops in an n-way mp environmentEP0384339B1Feb 19, 1990Apr 2, 1997Digital Equipment CorporationBroker for computer network server selectionEP0427874B1Jun 8, 1990Sep 6, 1995Asahi Kasei Kogyo Kabushiki KaishaPolyacetal copolymer and composition thereofEP0474340B1Jul 5, 1991May 19, 1999Bea Systems, Inc.Methods and apparatus for providing dynamic invocation of applicatons in a distributed heterogeneous environmentEP0555997B1Feb 4, 1993Oct 31, 2001AT&amp;T Corp.Apparatus and methods for implementing protocolsEP0565849A2Mar 5, 1993Oct 20, 1993International Business Machines CorporationA method and system for synchronizing threads within a processEP0569195B1Apr 29, 1993Mar 1, 2000Rockwell International CorporationTelephonic switching system with a user controlled data memory access system and methodEP0625750A3May 11, 1994Aug 16, 1995At & T CorpMethods and apparatus for making and using distributed applications.EP0635792B1Jun 29, 1994Aug 27, 2003Siemens AktiengesellschaftCoordination method for parallel access to resource configurations by a plurality of processorsEP0651328B1Oct 25, 1994Aug 9, 2000Microsoft CorporationEvent architecture for system management in an operating systemEP0660231B1Dec 9, 1994Aug 16, 2000Microsoft CorporationMethod and system for dynamically generating object connectionsEP0697655B1Aug 11, 1995Mar 27, 2002Canon Kabushiki KaishaSystem for managing external applications and filesEP0718761B1Dec 19, 1995Jul 12, 2000Sun Microsystems, Inc.A platform independent object and object viewer loader and methodEP0767432B1Sep 2, 1996Dec 19, 2001Sun Microsystems, Inc.System and method for distributed object resource managementEP0778520B1Nov 27, 1996May 4, 2005Sun Microsystems, Inc.System and method for executing verifiable programs with facility for using non-verifiable programs from trusted sourcesEP0794493B1Mar 5, 1997Jan 4, 2006Matsushita Electric Industrial Co., Ltd.Parallel distributed processing and operation processorsEP0803810A3Apr 23, 1997Feb 23, 2000Sun Microsystems, Inc.System and method for generating identifiers for uniquely identifying object typesEP0803811A3Apr 23, 1997Dec 6, 2000Sun Microsystems, Inc.System and method for stub retrieval and loadingEP0805393B1Apr 1, 1997Nov 9, 2011International Business Machines CorporationMethod and apparatus for managing membership of a group of processors in a distributed computing environmentEP0810524B1May 27, 1997May 7, 2003Sun Microsystems, Inc.Apparatus and method for processing servletsEP0817020B1Jul 1, 1997Sep 29, 2004Sun Microsystems, Inc.A name service for a redundant array of internet serversEP0817022A2May 9, 1997Jan 7, 1998Sun Microsystems, Inc.Method and apparatus for marshalling and unmarshalling argument object referencesEP0817025A3May 14, 1997Nov 12, 2003Sun Microsystems, Inc.Data structures and method for implementing subcontracts in a distributed object oriented systemGB2253079A Title not availableGB2262825B Title not availableGB2305087B Title not availableJP1145187A Title not available* Cited by examinerNon-Patent CitationsReference1"Change-Notification Service for Shared Files," IBM Technical Disclosure Bulletin, vol. 36, No. 8, pp. 77-82, XP002108713, New York, US, Aug. 1993.2"Resource Preemption for Priority Scheduling," IBM Technical Disclosure Bulletin, vol. 16, no. 6, p. 1931 XP002109435 New York, US, Nov. 1973.3Agha et al., Actorspaces: An Open Distributed Progamming Paradigm, University of Illinois, Report No. UIUCDCS-R-92-1766, Open Systems Laboratory TR No. 8, Nov. 1992, pp. 1-12.4Ahmed et al., A Program Building Tool for Parallel Applications, Yale University, Dec. 1, 1993, pp. 1-23.5Aldrich et al., "Providing Easier Access to Remote Objects in Client-Server Systems," System Sciences, 1998, Proceedings of the 31st Hawaii Internat'l. Conference, Jan. 6-9, 1998, pp. 366-375.6Aldrich et al., "Providing Easier Access to Remote Objects in Distributed Systems," Calif. Institute of Technology, www.cs.caltech.edu/%7Ejedi/paper/jedipaper.html, Nov. 21, 1997.7Alexander et al., "Active Bridging," Proceedings of the ACM/SIGCOMM'97 Conference, Cannes, France, Sep. 1997.8Anderson et al., Persistent Linda: Linda+Transactions+Query Processing, Proceedings of the 13th Symposium on Fault Tolerant Systems, 1994, pp. 93-109.9Beech et al., "Object Databases as Generalizations of Relational Databases," Computer Standards & Interfaces, Vo 13, Nos. 1/3 pp. 221-230, Amsterdam, NL, Jan. 1991.10Bertino et al., "Object-Oriented Database Management Systems: Concepts and Issues," Computer, Vol. 24, No. 4, pp. 33-47, Los Alamitos, CA, Apr. 1991.11Betz, "Interoperable Objects: Laying the Foundation for Distributed Object Computing," Dr. Dobb's Journal, Vol. 19, No. 11, p. 18(13), Oct. 1994.12Bevan, "An Efficient Reference Counting Solution To The Distributed Garbage Collection Problem," Parallel Computing, NL, Elsevier Science Publishers, Amsterdam, Vol. 9, No. 2, pp. 179-192, Jan. 1989.13Birrell et al., Grapevine: An Exercise in Distributed Computing, Communications of the ACM, vol. 25, No. 4, Apr. 1982, pp. 260-274.14Birrell et al., Network Objects, DEC SRC Research Report 115, Feb. 28, 1994.15Birrell, Andrew D. and Nelson, Bruce Jay, "Implementing Remote Procedure Calls, ACM Transactions on Computer Systems," vol. 2, No. 1, pp. 39-59, Feb. 1984.16Birrell, Andrew, et al., "Distributed Garbage Collection for Network Objects," Digital Systems Research Center, No. 116, Dec. 15, 1993, pp. 1-18.17Birrell, Andrew, et al., "Network Objects," Digital Equipment Corp. Systems Research Center Technical Report, 27(5), Dec. 1993, pp. 217-230.18Birrell, Andrew, et al., "Network Objects," Digital Systems Research Center, Proceedings of the Fourteenth ACM Symposium on Operating Systems Principles, vol. 27, No. 5, pp. 217-230, Dec. 1993.19Cannon et al., Adding Fault-Tolerant Transaction Processing to Linda, Software-Practice and Experience, vol. 24(5), May 1994, pp. 449-446.20Cardelli, Obliq, A lightweight language for network objects, Nov. 5, 1993, pp. 1-37.21Carriero et al, Distributed Data Structures in Linda, Yale Research Report YALEU/DCS/RR-438, Nov. 1985.22Carriero et al., Distributed Data Structures in Linda, Principals of Programming Language, 1986, pp. 1-16.23Chun, Kin-Man and Yuen, Herbert, "A "Tiny' Pascal Compiler: Part 2: The P-Compiler," BYTE Publications, Inc., pp. 34-52, Oct. 1978.24Chun, Kin-Man and Yuen, Herbert, "A ‘Tiny’ Pascal Compiler: Part 2: The P-Compiler," BYTE Publications, Inc., pp. 34-52, Oct. 1978.25Chung, Kin-Man and Yuen, Herbert, "A "Tiny' Pascal Compiler: Part 1: The P-Code Interpreter," BYTE Publications, Inc., pp. 58-155, Sep. 1978.26Chung, Kin-Man and Yuen, Herbert, "A "Tiny' Pascal Compiler: Part 2: The P-Compiler," BYTE Publications, Inc., Oct. 1978.27Chung, Kin-Man and Yuen, Herbert, "A "Tiny' Pascal Compiler: The P-Code Interpreter," BYTE Publications, Inc., Sep. 1978.28Chung, Kin-Man and Yuen, Herbert, "A ‘Tiny’ Pascal Compiler: Part 1: The P-Code Interpreter," BYTE Publications, Inc., pp. 58-155, Sep. 1978.29Chung, Kin-Man and Yuen, Herbert, "A ‘Tiny’ Pascal Compiler: Part 2: The P-Compiler," BYTE Publications, Inc., Oct. 1978.30Chung, Kin-Man and Yuen, Herbert, "A ‘Tiny’ Pascal Compiler: The P-Code Interpreter," BYTE Publications, Inc., Sep. 1978.31Coulouris et al., Distributed Systems Concepts and Designs, Second Edition, Addison-Wesley, 1994.32Dave et al., "Proxies, Application Interface, And Distributed Systems," Proceedings International Workshop On Object Orientation In Operating Systems, pp. 212-220, Sep. 24, 1992.33Dave et al., "Proxies, Application Interfaces, and Distributed Systems," XP 002009478, IEEE, 1992, pp. 212-220.34Deux et al., "The O2 System," Communications Of The Association For Computing Machinery, Vol. 34, No. 10, pp. 34-48, Oct. 1, 1991.35Dijkstra, Self-stabilizing Systems in Spite of Distributed Control, Communications of the ACM, vol. 17, No. 11, Nov. 1974, pp. 643-644.36Dolev et al., On the Minimal Synchronism Needed for Distributed Consensus, Journal of the ACM, vol. 34, No. 1, Jan. 1987, pp. 77-97.37Dollimore et al., "The Design of a System for Distributing Shared Objects," The Computer Journal, No. 6, Cambridge, GB, Dec. 1991.38Dourish, A Divergence-Based Model of Synchrony and Distribution in Collaborative Systems, Xerox Technical Report EPC-1194-102, 1994, pp. 1-10.39Droms, "RFC 1541 Dynamic Host Configuration Protocol," <http://www.cis.ohio-state.edu/htbin/rfc/rfc1541.html>, pp. 1-33, Oct. 1993.40Emms, "A Definition Of An Access Control Systems Language," Computer Standards And Interfaces, Vol. 6, No. 4, pp. 443-454, Jan. 1, 1987.41Fleisch et al., "High Performance Distributed Objects Using Distributed Shared Memory & Remote Method Invocation," System Sciences, 1998, Proceedings of the 31st Hawaii Internat'l. Conference, Jan. 6-9, 1998, pp. 574-578.42Gelernter et al., Parallel Programming in Linda, Yale University, Jan. 1985, pp. 1-21.43Gelernter, Generative Communication in Linda, ACM Transactions on Programming Languages and Systems, vol. 7, No. 1, Jan. 1985, pp. 80-112.44Gosling et al., "The Java (TM) Language Specification," Addison-Wesley, 1996.45Gottlob et al., "Extending Object-Oriented Systems with Roles," ACM Transactions On Information Systems, Vol. 14, No. 3, pp. 268-296, Jul. 1996.46Gray, Cary G. and Cheriton, David R., "Leases: An Efficient Fault-Tolerant Mechanism for Distributed File Cache Consistency," Computer Science Department, Stanford University, 1989.47Gray, Cary G., Et al., "Leases An Efficient Fault-Tolerant Mechanism for Distributed File Cache Consistency," Computer Science Department, Stanford University, 1989, pp. 202-210.48Guth, "JaveOne: Sun to Expand Java Distributed Computing Effort," <http://www.sunworld.com/swol-02-1998/swo-02-sunspots.html>, XP-002109935, P.1, Feb. 20, 1998.49Guyennet et al., "A New Consistency Protocol Implemented in the CAliF System," IEEE, 1094-7256/97, pp. 82-87, 1997.50Guyennet et al., "Distributed Shared Memory Layer for Cooperative Work Applications," IEEE, 0742-1303/97, pp. 72-78, 1997.51Hamilton et al., "Subcontract: A Flexible Base For Distributed Programming," Proceedings of 14th Symposium of Operating System Principles, Dec. 1993.52Hamilton, Marc A., "Java and the Shift to net-Centric Computing," Computer, Aug. 1996, pp. 31-39.53Harris et al., Proposal for a General Java Proxy Class for Distributed Systems and Other Uses, Netscape Communications Corp., Jun. 25, 1997.54Hartman et al., "Liquid Software: A New Paradigm For Networked Systems," Technical Report 96-11, Department of Comp. Sci., Univ. of Arizona, Jun. 1996.55Howard et al., Scale and Performance in a Distributed File System, ACM Transactions on Computer Systems, vol. 6, No. 1, Feb. 1988, pp. 51-81.56Hunt, "IDF: A Graphical Data Flow Programming Language for Image Processing and Computer Vision," Proceedings of the International Conference on Systems, Man, and Cybernetics, pp. 351-360, Los Angeles, Nov. 4-7, 1990.57IBM (TM) Technical Disclosure Bulletin, "Object Location Algorithm," Vol. 36, No. 09B, pp. 257-258, Sep. 1993.58IBM (TM) Technical Disclosure Bulletin, "Retrieval of Qualified Variables Using Extendible Hashing," Vol. 36, No. 12, pp. 301-303, Dec. 1993.59IBM Technical Disclosure Bulletin, "Local Network Monitoring to Populate Access Agent Directory," vol. 36, No. 09A, pp. 403-405, Sep. 1993.60IBM, "Chapter 6-Distributed SOM (DSOM)," SOMobjects Developer Toolkit Users Guide, Version 2.1, pp. 6-1-6-90, Oct. 1994.61IBM, "Chapter 6—Distributed SOM (DSOM)," SOMobjects Developer Toolkit Users Guide, Version 2.1, pp. 6-1-6-90, Oct. 1994.62Jaworski, Java 1.1 Developer's Guide, Sams.net, 1997.63Jones et al., "Garbage Collection-Algorithms For Automatic Dynamic Memory Management," John Wiley & Sons, 1996.64Jones et al., "Garbage Collection—Algorithms For Automatic Dynamic Memory Management," John Wiley & Sons, 1996.65Jones, Richard, et al., "Garbage Collection: Algorithms for Automatic Dynamic Memory Management," John Wiley & Sons, 1996.66Kambhatla et al., Recovery with Limited Replay: Fault-Tolerant Processes in Linda, Oregon Graduate Institute, Technical Report CSIE 90-019, Sep. 1990, pp. 1-16.67Kay et al., "An Overview of the Raleigh Object-Oriented Database System," ICL Technical Journal, Vol. 7, No. 4, pp. 780-798, Oxford, GB, Nov. 1991.68Kougiouris et al., "Support for Space Efficient Object Invocation in Spring," Sep. 1994.69Krasner, The Smalltalk-80 Virtual Machine, BYTE Publications Inc., Aug. 1991, pp. 300-320.70Lamport et al., The Byzantine Generals Problem, ACM Transactions on Programming Languages and Systems, vol. 4, No. 3, Jul. 1982, pp. 382-401.71Linda Database Search, Jul. 20, 1995, pp. 1-68.72Lindholm et al., "The Java (TM) Virtual Machine Specification," Addison Wesley, 1996.73Liskov et al., Distributed Object Management in Thor, International Workshop on Distributed Object Management, 1992, p. 12.74McDaniel, Gene, "An Analysis of a Mesa Instruction Set," Xerox Corporation, Palo Alto Research Center, May 1982.75Mitchell et al., "An Overview of the Spring System," Feb. 1994.76Mitchell, James G., et al., "Mesa Language Manual," Xerox Corporation, Palo Alto Research Centers.77Mullender, Distributed Systems, Second Edition, Addison-Wesley, 1993.78Mummert et al., Long Term Distributed File Reference Tracing: Implementation and Experience, Carnegie Mellon University School of Computer Science, Nov. 1994, pp. 1-28.79MUX-Elektronik, Java 1.1 Interactive Course, www.lls.se/~mux/javaic.html, 1995.80MUX-Elektronik, Java 1.1 Interactive Course, www.lls.se/˜mux/javaic.html, 1995.81Orfali et al., "The Essential Distributed Objects Survival Guide," Chapter 11: Corba Commercial ORBs, pp. 203-215, John Wiley & Sons, Inc., 1996.82Ousterhout et al., The Sprite Network Operating System, Computer, IEEE, Feb. 1988, pp. 23-36.83Pier, Kenneth A., "A Retrospective on the Dorado, A High-Performance Personal Computer," Conference Proceedings, The 10th Annual International Symposium on Computer Architecture, Royal Institute of Technology, Stockholm, Sweden, 1983.84Pier, Kenneth A., "A Retrospective on the Dorado, A High-Performance Personal Computer," Xerox Corporation, Palo Alto Research Centers, Aug. 1983.85Pier, Kenneth A., "A Retrospective on the Dorando, A High-Performance Personal Computer," IEEE Conference Proceedings, The 10th Annual International Symposium on Computer Architecture, 1983.86Pier, Kenneth A., "A Retrospective on the Dorando, A High-Performance Personal Computer," Xerox Corporation, Aug. 1983.87Pinakis, Using Linda as the Basis of an Operating System Microkernel, University of Western Australia, Department of Computer Science, Aug. 1993, pp. 1-165.88Remote Method Invocation Specification, Sun Microsystems, Inc., (1997), http://java.sun.com/products/jdk/1.1/docs/guide/rmi/spec/rmiTOC.doc.html.89Riggs et al., "Picking State in the Java (TM) System," USENIX Association Conference on Object-Oriented Technologies and Systems, XP-002112719, pp. 241-250, Jun. 17-21, 1996.90Rosenberry et al., "Understanding DCE," Chapters 1-3, 6, 1992.91Sharrott et al., ObjectMap: Integrating High Performance Resources into a Distributed Object-oriented Environment, ICODP, 1995.92Stevenson, "Token-Based Consistency of Replicated Servers," IEEE, CH2686-4/89/0000/0179, pp. 179-183, 1989.93Thompson, Ken, "Regular Expression Search Algorithm," Communications of the ACM, vol. II, No. 6, p. 149 et seq., Jun. 1968.94Thompson, Ken, "Regular Expression Search Algorithm," Programming Techniques, Communications of the ACM, vol. 11, No. 6, pp. 419-422, Jun., 1968.95Transparent Network Computing, Locus Computing Corporation, Jan. 5, 1995.96Waldo et al., "Events In An RPC Based Distributed System," Proceedings Of The 1995 USENIX Technical Conference, Proceedings USENIX Winter 1995 Technical Conference, New Orleans, LA, USA, 16-20, pp. 131-142, Jan. 1995.97Wilson, P.R., et al., "Design of the Opportunistic Garbage Collector," Proceedings of the Object Oriented Programming Systems Languages An Applications Conference, New Orleans, vol. 24, No. 10, Oct. 1989.98Wollrath et al., A Distributed Object Model for the Java(TM) System, USENIX Association, Conference on Object-Oriented Technologies and Systems, Jun. 17-21, 1996.99Wollrath et al., A Distributed Object Model for the Java™ System, USENIX Association, Conference on Object-Oriented Technologies and Systems, Jun. 17-21, 1996.100Wu, "A Type System For An Object-Oriented Database System," Proceedings of the International Computer Software and Applications Conference (COMPSAC), Tokyo, Japan, pp. 333-338, Sep. 11-13, 1991.101Yemini et al., "Towards Programmable Networks," IFIP/IEEE International Workshop on Distributed Systems: Operations and Management, L'Aquila, Italy, Oct. 1996.Referenced byCiting PatentFiling datePublication dateApplicantTitleUS6463468 *Jun 1, 1999Oct 8, 2002Netzero, Inc.Targeted network video download interfaceUS6564240Feb 20, 2002May 13, 2003Sun Microsystems, Inc.Method, apparatus, and product for leasing of group membership in a distributed systemUS6567820Nov 21, 2000May 20, 2003Sun Microsystems, Inc.Method and system for in-place modifications in a databaseUS6604127 *Jul 27, 2001Aug 5, 2003Brian T. MurphyDynamic lookup service in distributed systemUS6611858 *Nov 5, 1999Aug 26, 2003Lucent Technologies Inc.Garbage collection method for time-constrained distributed applicationsUS6629154Oct 12, 2000Sep 30, 2003Sun Microsystems, Inc.Method and system for deterministic hashes to identify remote methodsUS6654793Jun 30, 1998Nov 25, 2003Sun Microsystems, Inc.System and method for facilitating dynamic loading of stub information to enable a program operating in one address space to invoke processing of a remote method or procedure in another address spaceUS6704756May 14, 2001Mar 9, 2004Sun Microsystems, Inc.Methods, apparatus, and product for distributed garbage collectionUS6728737Feb 15, 2002Apr 27, 2004Sun Microsystems, Inc.Method and system for leasing storageUS6728847 *Nov 22, 2000Apr 27, 2004Farstone Technology, Inc.Network backup/recovery system and method regarding the sameUS6760736Dec 20, 2000Jul 6, 2004Sun Microsystems, Inc.Methods and systems for distributed failure detection and recovery using leasing techniquesUS6772162Nov 6, 2002Aug 3, 2004Sun Microsystems, Inc.Lease renewal serviceUS6816875Jun 19, 2003Nov 9, 2004Sun Microsystems IncMethods, apparatus, and product for distributed garbage collectionUS6832223Mar 20, 1998Dec 14, 2004Sun Microsystems, Inc.Method and system for facilitating access to a lookup serviceUS6895401 *May 13, 2003May 17, 2005Sun Microsystems, Inc.Method and apparatus of performing active update notificationUS6950874 *Dec 15, 2000Sep 27, 2005International Business Machines CorporationMethod and system for management of resource leases in an application framework systemUS6983285May 10, 2002Jan 3, 2006Sun Microsystems, Inc.Apparatus and method for dynamically verifying information in a distributed systemUS7089263May 10, 2002Aug 8, 2006Sun Microsystems, Inc.Apparatus and method for dynamically verifying information in a distributed systemUS7240110Apr 29, 2004Jul 3, 2007Netzero, Inc.Internet service error trackingUS7272649 *Sep 30, 1999Sep 18, 2007Cisco Technology, Inc.Automatic hardware failure detection and recovery for distributed max sessions serverUS7565533Jul 21, 2009Sun Microsystems, Inc.Systems and methods for providing object integrity and dynamic permission grantsUS7581006 *May 29, 1998Aug 25, 2009Yahoo! Inc.Web serviceUS7644408Jan 5, 2010Spotware Technologies, Inc.System for assigning and monitoring grid jobs on a computing gridUS7660887Feb 9, 2010Sun Microsystems, Inc.Systems and methods for providing dynamic quality of service for a distributed systemUS7673045 *Jun 15, 2000Mar 2, 2010Microsoft CorporationMultiple site automated logoutUS7734747Sep 25, 2003Jun 8, 2010Oracle America, Inc.Dynamic lookup service in a distributed systemUS7756969Jan 30, 2004Jul 13, 2010Oracle America, Inc.Dynamic provisioning of identification services in a distributed systemUS7792874Sep 7, 2010Oracle America, Inc.Dynamic provisioning for filtering and consolidating eventsUS7895651Feb 22, 2011Bit 9, Inc.Content tracking in a network security systemUS7925732Sep 11, 2007Apr 12, 2011Cisco Technology, Inc.Automatic hardware failure detection and recovery for distributed max sessions serverUS8078715Oct 19, 2010Dec 13, 2011Cisco Technology, Inc.Automatic hardware failure detection and recovery for distributed max sessions serverUS8103760Jan 24, 2012Oracle America, Inc.Dynamic provisioning of service components in a distributed systemUS8108347Jan 31, 2012Yahoo! Inc.Web server content replicationUS8185566 *May 22, 2012Microsoft CorporationClient-based caching of remote filesUS8272058Sep 18, 2012Bit 9, Inc.Centralized timed analysis in a network security systemUS8341458 *Dec 25, 2012International Business Machines CorporationControlling data consistency guarantees in storage apparatusUS8458216Feb 10, 2012Jun 4, 2013Microsoft CorporationClient-based caching of remote filesUS8713089Apr 8, 2003Apr 29, 2014Oracle America, Inc.Dynamic lookup service in a distributed systemUS8732202 *May 21, 2013May 20, 2014Microsoft CorporationAccess requests with cache intentionsUS8868606May 21, 2013Oct 21, 2014Microsoft CorporationClient-based caching of remote filesUS8984636Jul 29, 2005Mar 17, 2015Bit9, Inc.Content extractor and analysis systemUS9069782Sep 30, 2013Jun 30, 2015The Research Foundation For The State University Of New YorkSystem and method for security and privacy aware virtual machine checkpointingUS9076012Mar 11, 2014Jul 7, 2015Microsoft Technology Licensing, LlcAccess requests with cache intentionsUS9183066May 6, 2002Nov 10, 2015Oracle America Inc.Downloadable smart proxies for performing processing associated with a remote procedure call in a distributed systemUS9357029May 22, 2015May 31, 2016Microsoft Technology Licensing, LlcAccess requests with cache intentionsUS20020078213 *Dec 15, 2000Jun 20, 2002Ching-Jye ChangMethod and system for management of resource leases in an application framework systemUS20020091874 *Aug 3, 2001Jul 11, 2002Sun Microsystems, Inc.Deferred reconstruction of objects and remote loading for event notification in a distributed systemUS20020124118 *Jan 4, 2001Sep 5, 2002Colley Adrian E.Method and system for passing objects in a distributed system using serializatin contextsUS20030023613 *May 10, 2002Jan 30, 2003Sun Microsystems, Inc.Apparatus and method for dynamically verifying information in a distributed systemUS20030105147 *Oct 22, 2002Jun 5, 2003Synaptic Pharmaceutical CorporationBenzimidazoles and benzothiazoles and uses thereofUS20030204517 *May 13, 2003Oct 30, 2003Brian SkinnerMethod and apparatus of performing active update notificationUS20040030777 *Mar 19, 2003Feb 12, 2004Reedy Dennis G.Systems and methods for providing dynamic quality of service for a distributed systemUS20040215590 *Apr 25, 2003Oct 28, 2004Spotware Technologies, Inc.System for assigning and monitoring grid jobs on a computing gridUS20040216150 *Nov 5, 2002Oct 28, 2004Sun Microsystems, Inc.Systems and methods for providing object integrity and dynamic permission grantsUS20050021744 *Apr 29, 2004Jan 27, 2005Stacy HaitsukaInternet service error trackingUS20060010234 *Aug 30, 2005Jan 12, 2006Sun Microsystems Inc.Dynamic provisioning of service components in a distributed systemUS20060015507 *Jul 14, 2005Jan 19, 2006Butterworth Henry EControlling data consistency guarantees in storage apparatusUS20060026262 *Aug 4, 2005Feb 2, 2006Freeland AbbottContent collectionUS20070198723 *Jan 18, 2007Aug 23, 2007Samsung Electronics Co., Ltd.Apparatus and method for managing resources in containment framework environmentUS20080005328 *Sep 11, 2007Jan 3, 2008Cisco Technology, Inc. A California CorporationAutomatic hardware failure detection and recovery for distributed max sessions serverUS20100185704 *Jul 22, 2010Microsoft CorporationClient-based caching of remote filesUS20110035496 *Oct 19, 2010Feb 10, 2011Cisco Technology, Inc., A California CorporationAutomatic hardware failure detection and recovery for distributed max sessions serverCN100549965CFeb 15, 2007Oct 14, 2009三星电子株式会社Apparatus and method for managing resources in containment framework environmentEP1821213A1 *Feb 9, 2007Aug 22, 2007Samsung Electronics Co., Ltd.Apparatus and method for managing ressources in containment framework environment* Cited by examinerClassifications U.S. Classification1/1, 711/E12.009, 709/203, 711/E12.01, 709/219, 709/224, 711/E12.006, 709/229, 707/999.202, 707/999.01International ClassificationH04L29/06, G06F12/00, H04L12/417, H04L12/433, G06F17/30, G06F9/46, G06F9/50, G06F12/02, G06F9/445Cooperative ClassificationG06F9/5022, Y10S707/99957, Y10S707/99944, Y10S707/99953, Y10S707/99933, Y10S707/99952, H04L29/06, H04L12/433, G06F12/0253, G06F9/5016, G06F17/30607, G06F9/4411, G06F9/465, G06F9/5061, G06F9/547, G06F12/0261, G06F12/023, G06F9/5055, H04L12/417, G06F9/52, G06F9/5011, H04L69/24European ClassificationH04L29/06, H04L12/417, G06F9/46M, H04L12/433, G06F17/30S8T, G06F9/50A6S, G06F9/50A2M, G06F9/50A2, G06F9/52, G06F9/54P, G06F9/44A4, G06F12/02D2G2, G06F12/02D2, G06F12/02D2G, G06F9/50CLegal EventsDateCodeEventDescriptionNov 9, 2004FPAYFee paymentYear of fee payment: 4Nov 6, 2008FPAYFee paymentYear of fee payment: 8Dec 5, 2012FPAYFee paymentYear of fee payment: 12RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services