WO1999044130A1 - Method, apparatus, and product for leasing of delegation certificates in a distributed system - Google Patents
Method, apparatus, and product for leasing of delegation certificates in a distributed system Download PDFInfo
- Publication number
- WO1999044130A1 WO1999044130A1 PCT/US1999/003400 US9903400W WO9944130A1 WO 1999044130 A1 WO1999044130 A1 WO 1999044130A1 US 9903400 W US9903400 W US 9903400W WO 9944130 A1 WO9944130 A1 WO 9944130A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- resource
- lease
- delegatee
- access
- component
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/42—Loop networks
- H04L12/427—Loop networks with decentralised control
- H04L12/433—Loop networks with decentralised control with asynchronous transmission, e.g. token ring, register insertion
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
- G06F12/023—Free address space management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
- G06F12/023—Free address space management
- G06F12/0253—Garbage collection, i.e. reclamation of unreferenced memory
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
- G06F12/023—Free address space management
- G06F12/0253—Garbage collection, i.e. reclamation of unreferenced memory
- G06F12/0261—Garbage collection, i.e. reclamation of unreferenced memory using reference counting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/289—Object oriented databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4411—Configuring for operating with peripheral devices; Loading of device drivers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/465—Distributed object oriented systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/468—Specific access rights for resources, e.g. using capability register
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
- G06F9/548—Object oriented; Remote method invocation [RMI]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/46—Indexing scheme relating to G06F9/46
- G06F2209/462—Lookup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/24—Negotiation of communication capabilities
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99939—Privileged access
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99951—File or database maintenance
- Y10S707/99952—Coherency, e.g. same view to multiple users
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99951—File or database maintenance
- Y10S707/99952—Coherency, e.g. same view to multiple users
- Y10S707/99953—Recoverability
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99951—File or database maintenance
- Y10S707/99956—File allocation
- Y10S707/99957—Garbage collection
Definitions
- This invention generally relates to data processing systems and, more particularly, to leasing delegation certificates in data processing systems.
- resource management involves allocating resources (e.g., memory) in response to requests as well as deallocating resources at appropriate times, for example, when the requesters no longer require the resources.
- resources e.g., memory
- deallocating resources at appropriate times, for example, when the requesters no longer require the resources.
- the resources contain data referenced by computational entities (e.g., applications, programs, applets, etc.) executing in the computers.
- each resource has a unique "handle" by which the resource can be referenced.
- the handle may be implemented in various ways, such as an address, array index, unique value, pointer, etc.
- Resource management is relatively simple for a single computer because the events indicating when resources can be reclaimed, such as when applications no longer refer to them or after a power failure, are easy to determine. Resource management for distributed systems connecting multiple computers is more difficult because applications in several different computers may be using the same resource.
- Disconnects in distributed systems can lead to the improper and premature reclamation of resources or to the failure to reclaim resources.
- multiple applications operating on different computers in a distributed system may refer to resources located on other machines. If connections between the computers on which resources are located and the applications referring to those resources are interrupted, then the computers may reclaim the resources prematurely. Alternatively, the computers may maintain the resources in perpetuity, despite the extended period of time that applications failed to access the resources.
- distributed garbage collection a facility provided by a language or runtime system for distributed systems that automatically manages resources used by an application or group of applications running on different computers in a network.
- garbage collection uses the notion that resources can be freed for future use when they are no longer referenced by any part of an application.
- Distributed garbage collection extends this notion to the realm of distributed computing, reclaiming resources when no application on any computer refers to them.
- Distributed garbage collection must maintain integrity between allocated resources and the references to those resources. In other words, the system must not be permitted to deallocate or free a resource when an application running on any computer in the network continues to refer to that resource.
- This reference-to-resource binding referred to as "referential integrity,” does not guarantee that the reference will always grant access to the 5 resource to which it refers. For example, network failures can make such access impossible.
- the integrity guarantees that if the reference can be used to gain access to any resource, it will be the same resource to which the reference was first given.
- 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.
- 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.
- some conventional reference counting schemes include "keep-alive” messages, which are also referred to as “ping back.”
- applications in the network send messages to the garbage collection system overseeing resources and indicate that the applications can still communicate. These messages prevent the garbage collection system from dropping references to resources. Failure to receive such a "keep-alive” message indicates that the garbage collection system can decrement the reference count for a resource and, thus, when the count reaches zero, the garbage collection system may reclaim the resource. This, however, can still result in the premature reclamation of resources following reference counts reaching zero from a failure to receive "keep-alive” messages because of network failures. This violates the referential integrity requirement.
- Another proposed method for resolving referential integrity problems in garbage collection systems is to maintain not only a reference count but also an identifier corresponding to each computational entity referring to a resource. See A. Birrell, et al., "Distributed Garbage Collection for Network Objects," No. 116, digital Systems Research Center, December 15, 1993. This method suffers from the same problems as the reference counting schemes. Further, this method requires the addition of unique identifiers for each computational entity referring to each resource, adding overhead that would unnecessarily increase communication within distributed systems and add storage requirements (i.e., the list of identifiers corresponding to applications referring to each resource).
- referential integrity is guaranteed without costly memory leaks by leasing resources for a period of time during which the parties in a distributed system, for example, an application holding a reference to a resource and the garbage collection system managing that resource, agree that the resource and a reference to that resource will be guaranteed. At the end of the lease period, the guarantee that the reference to the resource will continue lapses, allowing the garbage collection system to reclaim the resource. Because the application holding the reference to the resource and the garbage collection system managing the resource agree to a finite guaranteed lease period, both can know when the lease and, therefore, the guarantee, expires. This guarantees referential integrity for the duration of a reference lease and avoids the concern of failing to 7 free the resource because of network errors.
- the leasing technique can be applied to delegation certificates.
- a method for leasing delegation certificates comprises the steps of receiving a lease request from a client specifying a resource and a lease period, determining a lease period during which the client has authority to request from a server access to the resource, advising the client of the granted lease period, granting the client a delegation certificate which the client can use to access the resource from the server.
- FIG. 1 is a flow diagram of the steps performed by the application call processor according to an implementation of the present invention
- FIG. 2 is a flow diagram of the steps performed by the server call processor to process dirty calls according to the implementation of the present invention
- FIG. 3 is a flow diagram of the steps performed by the server call processor to process clean calls according to the implementation of the present invention
- FIG. 4 is a flow diagram of the steps performed by the server call processor to initiate a garbage collection process according to the implementation of the present invention.
- FIG. 5 is a diagram of a preferred flow of calls within a distributed processing system
- FIG. 6 is a block diagram of the components of the implementation of a method invocation service according to the present invention.
- FIG. 7 is a diagram of a distributed processing system that can be used in an implementation of the present invention.
- FIG. 8 is a diagram of the individual software components in the platforms of the distributed processing system according to the implementation of the present invention. 8
- FIG. 9 is a diagram of a data processing system for leasing delegation certificates in a distributed processing system that can be used in an altemative embodiment of the present invention.
- FIG. 10 is a flow diagram of the steps performed by the delegator process when another process (potential delegatee) requests a lease according to an altemative embodiment of the present invention.
- FIG. 11 A and FIG. 1 IB represent a flow diagram of the steps performed by a process (potential delegatee) when requesting a lease from the delegator process according to an altemative embodiment of the present invention.
- FIG. 12 is a flow diagram of the steps performed by the server when a delegatee requests access to a resource according to an altemative embodiment of the present invention.
- the present invention may be implemented by computers organized in a conventional distributed processing system architecture.
- the architecture for and procedures to implement this invention are not conventional, because they provide a distributed garbage collection scheme that ensures referential integrity and eliminates memory leaks.
- a method invocation (MI) component located in each of the computers in the distributed processing system implements the distributed garbage collection scheme of this invention.
- the MI component may consist of a number of software modules preferably written in the JAVATM programming language.
- 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 9 number of references to a reference 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.”
- a dirty call can include a requested time interval, called a lease period, for the reference to the resource.
- the managing MI component Upon receipt of the dirty call, the managing MI component sends a return call indicating a period for which the lease was granted.
- the managing MI component thus tracks the lease period for those references as well as the number of outstanding references. Consequently, when the reference count for a resource goes to zero or when the lease period for the resource expires, the managing MI component can reclaim the resource.
- An application call processor in an MI component performs the steps of the application call procedure 100 illustrated in FIG. 1.
- the server call processor in the managing MI component performs the steps of the procedures 200, 300, and 400 illustrated in FIGs. 2-4, respectively.
- the managing MI component's garbage collector performs conventional procedures to reclaim resources previously bound to references in accordance with instmctions from the server call processor. Accordingly, the conventional procedures of the garbage collector will not be explained.
- FIG. 1 is a flow diagram of the procedure 100 that the application call processor of the MI component uses to handle application requests for references to resources managed by the same or another MI component located in the distributed processing system.
- the application call processor sends a dirty call, including the resource's reference and a requested lease period to the managing MI component for the resource (step 110).
- the dirty call may be directed to the resource itself or to the managing MI component. 10
- the application call processor then waits for and receives a return call from the managing MI component (step 120).
- the return call includes a granted lease period during which the managing MI component guarantees that the reference of the dirty call will be bound to its resource. In other words, the managing MI component agrees not to collect the resource co ⁇ esponding to the reference of a dirty call for the grant period. If the managing MI component does not provide a grant period, or rejects the request for a lease, then the application call processor will have to send another dirty call until it receives a grant period.
- the application call processor monitors the application's use of the reference and, either when the application explicitly informs the application call processor that the reference is no longer required or when the application call processor makes this determination on its own (step 130), the application call processor sends a clean call to the managing MI component (step 140). In a manner similar to the method used for dirty calls, the clean call may be directed to the referenced resource and the managing MI component will process the clean call. Subsequently, the application call processor eliminates the reference from a list of references being used by the application (step 150).
- step 160 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 110 and 120 to ensure that the reference to the resource is maintained by the managing MI component on behalf of the application. 2. Server Call Processor
- the MI component's server call processor performs three main procedures: (1) handling dirty calls; (2) handling incoming clean calls; and (3) initiating a garbage collection cycle to reclaim resources at the appropriate time.
- FIG. 2 is a flow diagram of the procedure 200 that the MI component's server call processor uses to handle requests to reference resources, i.e., dirty calls, that the MI software component manages. These requests come from application call processors of MI components in the distributed processing system, including the application call processor of the same MI component as the server call processor handling requests.
- the server call processor receives a dirty call (step 210).
- the server call processor determines an acceptable grant period (step 220).
- the grant period may be the 11 same as the requested lease period or some other time period.
- the server call processor determines the appropriate grant period based on a number of conditions including the amount of resource required and the number of other grant periods previously granted for the same resource.
- the server call processor determines that a resource has not yet been allocated for the reference of a dirty call (step 230)
- the server call processor allocates the required resource (step 240).
- the server call processor then increments a reference count corresponding to the reference of a dirty call (step 250), sets the acceptable grant period for the reference-to- resource binding (step 260), and sends a return call to an application call processor with the grant period (step 270). In this way, the server call processor controls incoming dirty calls regarding references to resources under its control.
- Applications can extend leases by sending dirty calls with an extension request before current leases expire. As shown in procedure 200, a request to extend a lease is treated just like an initial request for a lease. ⁇ An extension simply means that the resource will not be reclaimed for some additional interval of time, unless the reference count goes to zero.
- 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.
- the server call processor When the server call processor receives a clean call with a reference to a resource that the MI component manages (step 310), the server call processor decrements a co ⁇ esponding reference count (step 320). The clean call may be sent to the resource, with the server call processor monitoring the resource and executing the procedure 300 to process the call. Subsequently, the server call processor sends a return call to the MI component that sent the clean call to acknowledge receipt (step 330). In accordance with this implementation of the present invention, a clean call to drop a reference may not be refused, but it must be acknowledged. 12
- the server call processor also initiates a garbage collection cycle to reclaim resources for which it determines that either no more references are being made to the resource or that the agreed lease period for the resource has expired.
- the procedure 400 shown in FIG. 4 includes a flow diagram of the steps that the server call processor uses to initiate a garbage collection cycle.
- the server call processor monitors reference counts and granted lease periods and determines whether a reference count is zero for a resource managed by the MI component, or the grant period for a reference has expired (step 410). When either condition exists, the server call processor initiates garbage collection (step 420) of that resource. Otherwise, the server call processor continues monitoring the reference counts and granted lease periods.
- FIG. 5 is a diagram illustrating the flow of calls among MI components within the distributed processing system.
- Managing MI component 525 manages the resources 530 by monitoring the references to those resources 530 (see garbage collect 505). Because the managing MI components 525 manages the resources, the server call processor of managing MI component 525 performs the operations of this call flow description.
- FIG. 5 also shows that applications 510 and 540 have corresponding MI components 515 and 545, respectively.
- Each of the applications 510 and 540 obtains a reference to one of the resources 530 and seeks to obtain access to one of the resources 530 such that a reference is bound to the corresponding resource.
- applications 510 and 540 invoke their co ⁇ esponding MI components 515 and 545, respectively, to send dirty calls 551 and 571, respectively, to the MI component 525.
- the MI components 515 and 525 handle application requests for access to resources 530 managed by another MI component, such as managing MI component 525, the application call processors of MI components 515 and 545 perform the operations of this call flow description.
- managing MI component 525 sends return calls 552 and 572, respectively, to each of the MI components 515 and 545, respectively.
- the dirty calls include granted lease periods for the references of the dirty calls 551 and 571. 13
- FIG. 5 also shows MI components 515 and 545 sending clean calls 561 and 581, respectively, to managing MI component 525.
- Clean calls 561 and 581 inform managing MI component 525 that applications 510 and 540, respectively, no longer require access to the resource specified in the clean calls 561 and 581.
- Managing MI component 525 responds to clean calls 561 and 581 with retum calls 562 and 582, respectively.
- Retum calls 562 and 582 differ from retum calls 552 and 572 in that retum calls 562 and 582 are simply acknowledgments from MI component 525 of the received clean calls 561 and 581.
- Both applications 510 and 540 may request access to the same resource.
- application 510 may request access to "RESOURCE(l)" 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(l)" 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.
- the present invention also permits an application to access a resource after it sent a clean call to the managing MI component dropping the reference to the resource. This occurs because the resource is still referenced by another application or the reference's lease has not yet expired so the managing MI component 525 has not yet reclaimed the resource. The resource, however, will be reclaimed after a finite period, either when no more applications have leases or when the last lease expires.
- FIG. 6 is a block diagram of the modules of an MI component 600 according to an implementation of the present invention.
- MI component 600 can include a reference component 605 for each reference monitored, application call processor 640, server call processor 650, and garbage collector 660.
- Reference component 605 preferably constitutes a table or comparable stmcture with reference data portions 610, reference count 620, and grant period register 630.
- MI component 600 uses the reference count 620 and grant period 630 for each reference specified in a corresponding reference data portion 610 to determine when to initiate garbage collector 660 to reclaim the corresponding resource. 14
- Application call processor 640 is the software module that performs the steps of procedure 100 in FIG. 1.
- Server call processor 650 is the software module that performs the steps of procedures 200, 300, and 400 in FIGs. 2-4.
- Garbage collector 660 is the software module that reclaims resources in response to instructions from the server call processor 650, as explained above.
- FIG. 7 illustrates a distributed processing system 50 which can be used to implement the present invention.
- distributed processing system 50 contains three independent and heterogeneous platforms 100, 200, and 300 connected in a network configuration represented by the network cloud 55.
- the composition and protocol of the network configuration represented in FIG. 7 by the cloud 55 is not important as long as it allows for communication of the information between platforms 700, 800 and 900.
- the use of just three platforms is merely for illustration and does not limit the present invention to the use of a particular number of platforms.
- the specific network architecture is not crucial to this invention. For example, another network architecture that could be used in accordance with this invention would employ one platform as a network controller to which all the other platforms would be connected.
- 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.
- Applications 720, 820, and 920 can be programs that are either previously written and modified to work with the present invention, or that are specially written to take advantage of the services offered by the present invention. Applications 720, 820, and 920 invoke operations to be performed in accordance with this invention.
- MI components 730, 830, and 930 correspond to the MI component 600 discussed above with reference to FIG. 6.
- Operating systems 740, 840, and 940 are standard operating systems tied to the corresponding processors 710, 810, and 910, respectively.
- the platforms 700, 800, and 900 can be heterogenous.
- platform 700 has an UltraSparc® microprocessor 15 manufactured by Sun Microsystems Corp. as processor 710 and uses a Solaris® operating system 740.
- Platform 800 has a MIPS microprocessor manufactured by Silicon Graphics Corp. as processor 810 and uses a Unix operating system 840.
- platform 900 has a Pentium microprocessor manufactured by Intel Corp. as processor 910 and uses a Microsoft Windows 95 operating system 940.
- the present invention is not so limited and could accommodate homogenous platforms as well.
- Sun, Sun Microsystems, Solaris, Java, and the Sun Logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. UltraSparc and all other SPJARC trademarks are used under license and are trademarks of SPARC International, Inc. in the United States and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.
- Memories 750, 850, and 950 serve several functions, such as general storage for the associated platform. Another function is to store applications 720, 820, and 920, MI components 730, 830, and 930, and operating systems 740, 840, and 940 before execution by the respective processor 710, 810, and 910. In addition, portions of memories 750, 850, and 950 may constitute shared memory available to all of the platforms 700, 800, and 900 in network 50.
- the present invention may be implemented using a client/server model.
- the client generates requests, such as the dirty calls and clean calls, and the server responds to requests.
- FIG. 7 preferably includes both client components and server components.
- FIG. 8 which is a block diagram of a client platform 1000 and a server platform 1100, applies to any two of the platforms 700, 800, and 900 in FIG. 7.
- 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.
- processor 1010 executes a client application 1020
- 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. 16
- MI components 1030 and 1130 each include a server call processor 1031 and 1131, respectively, an application call processor 1032 and 1132, respectively, and a garbage collector 1033 and 1133, respectively.
- Each of the MI components 1030 and 1130 also contains reference components, including reference data portions 1034 and 1134, respectively, reference counts 1035 and 1135, respectively, and grant period registers 1036 and 1136, respectively, for each reference that the respective MI component 1030 or 1130 monitors.
- Application call processors 1032 and 1132 represent the client service and communicate with server call processors 1031 and 1131, respectively, which represent the server service. Because platforms 1000 and 1100 contain a server call processor, an application call processor, a garbage collector, and reference components, either platform can act as a client or a server.
- platform 1000 is designated the client platform and platform 1100 is designated as the server platform.
- client application 1020 obtains references to distributed resources and uses MI component 1030 to send dirty calls to the resources managed by MI component 1130 of server platform 1100.
- server platfo ⁇ n 1100 may be executing a server application 1120.
- Server application 1120 may also use MI component 1130 to send dirty calls, which may be handled by MI component 1130 when the resources of those dirty calls are managed by MI component 1130.
- server application 1120 may use MI component 1130 to send dirty calls to resources managed by MI component 1030.
- server call processor 1031, garbage collector 1033, and reference count 1035 for MI component 1030 of client platform 1000 are not active and are therefore presented in FIG. 8 as shaded.
- application call processor 1132 of MI component 1130 of the server platform 1100 is shaded because it is also dormant.
- application call processor 1032 sends a dirty call, which server call processor 1131 receives.
- the dirty call includes a requested lease period.
- Server call processor 1131 increments the reference count 1135 for the reference in the dirty call and determines a grant period.
- server call processor 1131 sends a retum call to application call processor 1030 with the grant period.
- Application call processor 1032 uses the grant period to update 17 recorded grant period 1035, and to determine when the resource corresponding to the reference of its dirty call may be reclaimed.
- Server call processor 1131 also monitors the reference counts and grant periods corresponding to references for resources that it manages. When one of its reference counts 1135 is zero, or when the grant period 1135 for a reference has expired, whichever event occurs first, server call processor 1131 may initiate the garbage collector 1133 to reclaim the resource corresponding to the reference that has a reference count of zero or an expired grant period.
- the leased-reference scheme does not require that the clocks on the platforms 1000 and 1100 involved in the protocol be synchronized.
- the scheme merely requires that they have comparable periods of increase. Leases do not expire at a particular time, but rather expire after a specific time interval. As long as there is approximate agreement on the interval, platforms 1000 and 1100 will have approximate agreement on the granted lease period. Further, since the timing for the lease is, in computer terms, fairly long, minor differences in clock rate will have little or no effect.
- the transmission time of the dirty call can affect the protocol. If MI component 1030 holds a lease to reference and waits until just before the lease expires to request a renewal, the lease may expire before the MI component 1130 receives the request. If so, MI component 1130 may reclaim the resource before receiving the renewal request. Thus, when sending dirty calls, the sender should add a time factor to the requested lease period in consideration of transmission time to the platform handling the resource of a dirty call so that renewal dirty calls may be made before the lease period for the resource expires.
- a distributed garbage collection scheme ensures referential integrity and eliminates memory leaks by providing granted lease periods corresponding to references to resources in the distributed processing system such that when the granted lease periods expire, so do the references to the resources.
- the resources may then be collected. Resources may also be collected when they are no longer being referenced by processes in the distributed processing system with reference to counters assigned to the references for the resources.
- the leasing technique relates to garbage collection.
- an altemative embodiment of the present invention as described below, can be used with delegation certificates.
- a delegation certificate allows one actor (“a delegator”) with sufficient privilege to access a resource to delegate its authority to access this resource to another actor (“a delegatee”) who then accesses the resource on behalf of the delegator.
- the delegator may not want to delegate to the delegatee carte blanche permission to access the resource for fear the delegatee may abuse its privilege either intentionally or unintentionally.
- the delegator may want to impose limits on the delegatee's access, such as the type of access permitted or the length of time access is permitted.
- the leasing of delegation certificates allows the delegator to control and limit the delegatee's access, thus providing additional security.
- Delegation certificates can be leased to access various resources, such as files.
- An example of a delegation follows: a delegator may have confidential tax files managed by a file system manager. By prior negotiation, the file system manager will only grant access to these files to the owner, the delegator. However, the owner may need the taxes to be calculated by a tax program, so the owner delegates authority to the tax program, the delegatee, to access the tax files for a limited time, until April 15. Accordingly, the owner grants the tax program permission, via a delegation certificate, to access the files controlled by the file system manager until April 15th. This is accomplished by leasing the delegation certificate to the tax program such that the lease expires on April 15th. If the tax program attempts to access the file after this date, the lease expires and it is prevented from doing so by the file system manager.
- the leasing of delegation certificates allows the owner to control or limit access to the files by the tax program. More specifically, the tax program requests a lease from the owner for access to the files stored with the file system manager for read access until April 15th. If a lease is granted, the owner sends to the tax program a delegation certificate that indicates the tax program is entitled to read-only access to the owner's files.
- the file system manager has the responsibility of authenticating the delegation certificate as well as to determine the type and length of the tax program's access. At no time 19 can the tax program directly change the contents of the delegation certificate. However, the tax program can request the owner to renew the lease (i.e., if the tax program requires additional time to access the file) or to cancel the lease, (i.e., if the tax program's access is completed before the lease period expires).
- the delegation certificate is an object that proves the identity of the delegator and has a set of corresponding rights attached to it.
- the delegation certificate object contains a principal identifier, some means for proving the identification, and a specification of the rights.
- the specification of the rights includes methods for determining the type of access requested and the duration of a lease.
- the object includes methods for canceling a lease and for renewing a lease.
- the methods may generate exceptions that, when accessed, set forth the reason why invocation of the method was unsuccessful.
- the object is an instance of a class that may be extended in many ways to offer more functionality, but the basic class is defined as follows:
- the principal identifier gives the delegatee the appearance of being the delegator when the delegatee communicates with the system manager.
- the integrity of the identification is assured by any number of known authentication methods, such as public-key, challenge-response protocol, or shared secret technology.
- Invoking the access type method provides the type of access the delegator permits. This method can be invoked by whoever has the delegation certificate, either the delegator, the delegatee, or the file system manager. For instance, the delegatee will invoke the method 20 to determine what type of access it is permitted to seek from the file system manager. The file system manager will invoke the method to determine what type of access it is permitted to grant. For example, the delegator may deem a particular file as read-only access. In this case, the file system manager will only allow read access for a subsequently granted lease for that particular file. Conversely, an attempt by the delegatee to write to that storage location would not be permitted by the file system manager.
- Invoking the duration method provides the length of the granted lease period. This period represents the most recent lease granted by the delegator.
- the renew method permits the renew of the lease, asking for more time, without having to re-initiate the original lease request.
- Situations where the delegatee may desire to renew the lease include when the original lease proves to be insufficient (i.e., the delegatee requires additional use of the storage location), or when only a partial lease (i.e., less than the requested lease) is granted.
- the renew method can be continually invoked in order to obtain sequential lease periods.
- the renew method cannot be invoked if the delegatee does not have an active lease.
- the renew method has no retum 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 delegator is unable or unwilling to renew the lease, the reason is set forth in the LeaseDeniedException generated by the renew method.
- the cancel method is invoked when there is still time left on the lease, but the delegatee no longer desires access.
- the cancel method may also be invoked by the delegator if, for instance, it wants to cancel the delegatee's access.
- cancel allows the file, for example, to be reclaimed.
- end of a lease i.e., natural termination occurs
- Figure 9 depicts a data processing system 9000 suitable for use for by an altemative embodiment of the present invention.
- the data processing system 9000 includes a computer system 9002 connected to the Internet 9004.
- the computer system 9002 includes a memory 9010, a secondary storage device 9018, a central processing unit (CPU) 9024, an input device 9026, and a video display 9022.
- the secondary storage device 9018 further includes a number of files 9020.
- the memory 9010 further includes a delegator program 9008, a delegatee program 9010, and an operating system 9014 containing a file system manager 21
- the file system manager 9016 manages files 9020 on the secondary storage device 9018.
- the delegatee 9010 requests access to a secondary storage device 9018 by requesting a lease from the delegator 9008. In response, the delegator 9008 may either grant or deny the lease as further described below. If the delegator 9008 grants the lease to the delegatee 9010, the delegatee 9010 then requests access to the secondary storage device 9018 from the file system manager 9016.
- computer 9000 may contain additional or different components.
- Figure 10 depicts a flow chart of the steps performed by the delegator 9008 when receiving a lease request from the delegatee 9010.
- the first step performed by the delegator is to request the delegatee to access a resource, such as a file, on the delegator's behalf (step 10002).
- a lease request is a function call that includes a number of parameters including (1) the requested file the delegatee wishes to lease, (2) the desired lease period, and (3) the type of access the delegatee desires.
- the requested file parameter contains an indication of the file to be leased.
- the desired lease period contains an amount of time the delegatee wants to utilize the file.
- the type of access requested indicates the type of access the client requested. For example, the delegatee may request read access or write access. To form a valid request, the delegatee request must contain both the file desired and the desired lease. After receiving the request, the delegator examines the parameters to verify the propriety of the request (step 10006).
- the delegator determines if the request is, in fact, proper (step 10008). For example, the delegator checks if the requested file is a file that the delegator has the ability to lease. Also, the delegator verifies that some lease period is specified. Additionally, the delegator checks if the type of access requested is available. If the delegator determines that the lease request is improper, the delegator generates an exception (step 10010) and processing ends. 22
- the delegator determines a sufficient lease period (step 10012). For example, if access to the delegator's tax files are requested, the delegator may grant a lease period up to April 15. Next, the delegator creates a lease object and returns the object to the delegatee (step 10020) and processing ends.
- Figures 11 A and 1 IB depict a flowchart of the steps performed by the delegatee 9010 when requesting a lease from the delegator 9008.
- the first step performed by the potential delegatee is to receive a request by the delegatee that entails accessing a file on the delegator's behalf (step 11001).
- the delegatee sends a request for a lease to the delegator (step 11002). This request is a function call and is described in step 10004 in figure 10.
- the delegatee After sending the request, the delegatee receives a lease object from the delegator (step 11004).
- the lease object includes the principal identifier, the authentication method, the access-type method, the lease duration method, the renew method, the cancel method.
- the delegatee by examining the lease object, determines if a lease was granted (step 11006). If the delegatee determines that a lease was not granted, the delegatee invokes the exception method (step 11008), which allows the delegatee to determine why a lease was not granted. If the delegatee determines that the lease was not granted because of an improper request (step 11010), the delegatee reconfigures the request (step 11012), and processing continues to step 11002. However, if the delegatee determines that the lease was not granted for reasons other than an improper request, processing ends. Note, the delegator may grant multiple leases to the same file, since it is ultimately the responsibility of the file system manager to referee actual access to the file.
- step 11006 determines that a lease was granted by the delegator, next the delegatee requests access to the file from the file system manager, by sending an access request (step 11018). Processing then continues to step 11020 in Fig. 1 IB.
- the delegatee After the delegatee sends the access request to the file system manager in step 11018 in figure 11 A, the delegatee determines, by examining the lease object, if the file system manager granted the delegatee access to the file (step 11020). If the delegatee determines that access was not granted by the file system manager, the delegatee invokes the exception 23 method, contained in the object returned by the file system manager, which allows the delegatee to determine why access was not granted (step 11022).
- step 11024 If the delegatee determines that access was not granted because of an improper request (step 11024), processing ends. On the other hand, if the request was proper, the delegatee determines if access was not granted because the file system manager allocated the file to another leaseholder (step 11026). If the delegatee determines the file is busy, the delegatee waits for a predetermined period of time (step 11028) and processing continues to step 11018 in Fig. 11 A. If the delegatee determines that access to the file was denied for some other reason, processing ends.
- step 11020 If the delegatee determines, in step 11020, that the file system manager granted the delegatee access to the file, then the delegatee can access the file (step 11030). Next, the delegatee determines if it is finished accessing the file (step 11032).
- the delegatee determines if the lease expired, (i.e., the lease is no longer active) (step 11034). If the lease expired, processing ends and no communication is necessary between the delegatee and the file system manager (i.e., natural termination occurs). Otherwise, if the lease is still active the delegatee invokes the cancel method (step 11036). The delegatee accesses the cancel method via the lease object. The cancel method informs the file system manager and the delegator that the delegatee is no longer interested in the file. Accordingly, the cancel method allows the file system manager to reclaim the file for use by other lease holders in an expeditious fashion.
- the lease expired processing ends and no communication is necessary between the delegatee and the file system manager (i.e., natural termination occurs). Otherwise, if the lease is still active the delegatee invokes the cancel method (step 11036).
- the delegatee accesses the cancel method via the lease object.
- the cancel method informs the file system manager and the delegator that the delegatee is no longer interested
- step 11038 determines if the lease is about to expire. This is achieved by the delegatee comparing the duration of the lease with current time minus the time when the lease was granted. The duration of the lease is found by invoking the duration method. If the lease is not about to expire, the delegatee continues to access the file (step 11030).
- step 11040 the delegatee must decide whether or not to renew the lease (step 11040). If the delegatee chooses to renew the lease, the delegatee invokes the renew method of the lease object. If the renew method is invoked, processing continues to step 11002 in Fig. 11 A. If the delegatee does not renew the lease, then processing ends and no communication is necessary between the delegatee and the file system manager (i.e., natural termination occurs). 24
- Figure 12 depicts a flow chart of the steps perfo ⁇ ned by the file system manager 9016 when a delegatee process 9008 requests access to a file.
- the first step performed by the file system manager is to receive an access request by the delegatee (step 1202).
- the file system manager authenticates the delegatee's identity by invoking the principal identifier method and the authentication method, via the lease object (step 1203). If the file system manager determines that the delegatee's lacks the proper identity to access the file (step 1204), the file system manager generates an exception (step 1206) and processing ends.
- the file system manager determines in step 1204 that the delegatee's identity is authentic, invokes the getAccess type method (step 1208). By invoking the getAccess type method, the file system manager is able to determine which type of access the delegatee desires. Next, the file system manager determines if the file is available for the type of access requested (step 1210). If the file system manager determines that the file is unavailable, the file system manager generates an exception (step 1206) and processing ends.
- step 1212 the file system manager invokes the duration method.
- the file system manager invokes the duration method in order to determine if there is time left on the delegatee's lease. If the file system manager determines that the delegatee's lease is active (step 1214), the file system manager grants the delegatee access to the file (step 1218). After granting the delegatee access to the file, the file system manager returns to step 1212.
- step 1214 If the file system manager determines in step 1214 that the lease is not active, the file system manager will reclaim the file (step 1216). After reclaiming the file, the file system manager generates an exception (step 1206) and processing ends.
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP99936130A EP1062580A1 (en) | 1998-02-26 | 1999-02-17 | Method, apparatus, and product for leasing of delegation certificates in a distributed system |
KR1020007009396A KR20010041296A (en) | 1998-02-26 | 1999-02-17 | Method, apparatus, and product for leasing of delegation certificates in a distributed system |
JP2000533814A JP2002505470A (en) | 1998-02-26 | 1999-02-17 | Method, apparatus, and product for lease of delegated authentication in distributed system |
AU32972/99A AU3297299A (en) | 1998-02-26 | 1999-02-17 | Method, apparatus, and product for leasing of delegation certificates in a distributed system |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US7604898P | 1998-02-26 | 1998-02-26 | |
US60/076,048 | 1998-02-26 | ||
US09/044,838 US6247026B1 (en) | 1996-10-11 | 1998-03-20 | Method, apparatus, and product for leasing of delegation certificates in a distributed system |
US09/044,838 | 1998-03-20 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO1999044130A1 true WO1999044130A1 (en) | 1999-09-02 |
Family
ID=26722055
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US1999/003400 WO1999044130A1 (en) | 1998-02-26 | 1999-02-17 | Method, apparatus, and product for leasing of delegation certificates in a distributed system |
Country Status (7)
Country | Link |
---|---|
US (1) | US6247026B1 (en) |
EP (1) | EP1062580A1 (en) |
JP (1) | JP2002505470A (en) |
KR (1) | KR20010041296A (en) |
CN (1) | CN1298509A (en) |
AU (1) | AU3297299A (en) |
WO (1) | WO1999044130A1 (en) |
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2005013157A2 (en) | 2003-08-01 | 2005-02-10 | Oracle International Corporation | Dynamic reassignment of data ownership |
US7120651B2 (en) | 2003-08-01 | 2006-10-10 | Oracle International Corporation | Maintaining a shared cache that has partitions allocated among multiple nodes and a data-to-partition mapping |
US7139772B2 (en) | 2003-08-01 | 2006-11-21 | Oracle International Corporation | Ownership reassignment in a shared-nothing database system |
US8234517B2 (en) | 2003-08-01 | 2012-07-31 | Oracle International Corporation | Parallel recovery by non-failed nodes |
WO2013122977A1 (en) * | 2012-02-16 | 2013-08-22 | Citrix Systems, Inc. | Connection leasing for hosted services |
WO2019081911A1 (en) * | 2017-10-27 | 2019-05-02 | Improbable Worlds Ltd. | Handover techniques for simulation systems and methods |
US10303821B2 (en) | 2016-08-24 | 2019-05-28 | Improbable Worlds Ltd. | Load balancing systems and methods for spatially-optimized simulations |
US10380282B2 (en) | 2016-08-24 | 2019-08-13 | Improbable Worlds Ltd | Distributable and customizable load-balancing of data-associated computation via partitions and virtual processes |
US10579434B2 (en) | 2016-08-24 | 2020-03-03 | Improbable Worlds Ltd | Simulation systems and methods using query-based interest |
US10643010B2 (en) | 2016-08-24 | 2020-05-05 | Improbable Worlds Ltd | Scalable simulation system with scalable data propagation |
US10878146B2 (en) | 2016-08-24 | 2020-12-29 | Improbable Worlds Ltd | Handover techniques for simulation systems and methods |
US11087047B2 (en) | 2016-08-24 | 2021-08-10 | Improbable Worlds Ltd | Scalable update propagation via query aggregations and connection migrations |
US11416305B2 (en) | 2016-08-24 | 2022-08-16 | Improbable Worlds Limited | Commands for simulation systems and methods |
Families Citing this family (37)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6792424B1 (en) * | 1999-04-23 | 2004-09-14 | International Business Machines Corporation | System and method for managing authentication and coherency in a storage area network |
US6950874B2 (en) * | 2000-12-15 | 2005-09-27 | International Business Machines Corporation | Method and system for management of resource leases in an application framework system |
US7024662B2 (en) | 2001-03-14 | 2006-04-04 | Microsoft Corporation | Executing dynamically assigned functions while providing services |
US7302634B2 (en) | 2001-03-14 | 2007-11-27 | Microsoft Corporation | Schema-based services for identity-based data access |
CA2449953A1 (en) * | 2001-08-29 | 2003-03-06 | Psinaptic Inc. | Distributed networking system for resource-constrained computing devices |
US7047213B2 (en) * | 2001-10-03 | 2006-05-16 | International Business Machines Corporation | Method for purging abandoned shopping carts from an electronic commerce web site |
JP4186456B2 (en) * | 2001-11-28 | 2008-11-26 | 沖電気工業株式会社 | Distributed file sharing system and control method thereof |
US7367044B2 (en) * | 2002-06-14 | 2008-04-29 | Clink Systems, Ltd. | System and method for network operation |
US9886309B2 (en) * | 2002-06-28 | 2018-02-06 | Microsoft Technology Licensing, Llc | Identity-based distributed computing for device resources |
US7428751B2 (en) * | 2002-12-05 | 2008-09-23 | Microsoft Corporation | Secure recovery in a serverless distributed file system |
US8166101B2 (en) | 2003-08-21 | 2012-04-24 | Microsoft Corporation | Systems and methods for the implementation of a synchronization schemas for units of information manageable by a hardware/software interface system |
US8238696B2 (en) | 2003-08-21 | 2012-08-07 | Microsoft Corporation | Systems and methods for the implementation of a digital images schema for organizing units of information manageable by a hardware/software interface system |
US7366740B2 (en) * | 2004-05-03 | 2008-04-29 | Microsoft Corporation | Systems and methods for automatic maintenance and repair of enitites in a data model |
US7644239B2 (en) | 2004-05-03 | 2010-01-05 | Microsoft Corporation | Non-volatile memory cache performance improvement |
US7490197B2 (en) | 2004-10-21 | 2009-02-10 | Microsoft Corporation | Using external memory devices to improve system performance |
TWI298128B (en) * | 2005-10-20 | 2008-06-21 | Ind Tech Res Inst | Method and system for managing distributed storage of digital contents |
JP4854000B2 (en) * | 2005-11-02 | 2012-01-11 | 株式会社日立ソリューションズ | Confidential file protection method |
KR100785782B1 (en) * | 2005-11-17 | 2007-12-18 | 한국전자통신연구원 | System of Privilege Delegation and Method Thereof |
US8914557B2 (en) | 2005-12-16 | 2014-12-16 | Microsoft Corporation | Optimizing write and wear performance for a memory |
KR100714124B1 (en) * | 2006-02-21 | 2007-05-02 | 한국전자통신연구원 | Method and apparatus for issuing certificate with user consent |
US7941801B2 (en) * | 2006-03-07 | 2011-05-10 | Oracle America Inc. | Method and system for provisioning a virtual computer and scheduling resources of the provisioned virtual computer |
US7707290B2 (en) * | 2006-05-08 | 2010-04-27 | International Business Machines Corporation | Securing leased resources on a computer |
US8185960B1 (en) | 2006-07-27 | 2012-05-22 | Qlogic, Corporation | System and method for managing access to adapter features |
US20090063240A1 (en) * | 2007-08-30 | 2009-03-05 | Oracle International Corporation | Routing transactions in a multiple job environment using an approval framework |
US8321919B2 (en) * | 2007-09-05 | 2012-11-27 | Oracle International Corp. | Framework for delegating roles in human resources ERP systems |
US8631203B2 (en) | 2007-12-10 | 2014-01-14 | Microsoft Corporation | Management of external memory functioning as virtual cache |
US8452947B2 (en) * | 2008-02-01 | 2013-05-28 | International Business Machines Corporation | Hardware wake-and-go mechanism and content addressable memory with instruction pre-fetch look-ahead to detect programming idioms |
US8612977B2 (en) * | 2008-02-01 | 2013-12-17 | International Business Machines Corporation | Wake-and-go mechanism with software save of thread state |
US7987163B2 (en) * | 2008-02-12 | 2011-07-26 | Bae Systems Information And Electronic Systems Integration Inc. | Apparatus and method for dynamic web service discovery |
US8402508B2 (en) * | 2008-04-02 | 2013-03-19 | Microsoft Corporation | Delegated authentication for web services |
US9032151B2 (en) | 2008-09-15 | 2015-05-12 | Microsoft Technology Licensing, Llc | Method and system for ensuring reliability of cache data and metadata subsequent to a reboot |
US8032707B2 (en) | 2008-09-15 | 2011-10-04 | Microsoft Corporation | Managing cache data and metadata |
US7953774B2 (en) | 2008-09-19 | 2011-05-31 | Microsoft Corporation | Aggregation of write traffic to a data store |
US20110022662A1 (en) | 2009-07-23 | 2011-01-27 | International Business Machines Corporation | Event triggered notifications for collaborative processes |
US9396089B2 (en) | 2014-05-30 | 2016-07-19 | Apple Inc. | Activity tracing diagnostic systems and methods |
US10430577B2 (en) * | 2014-05-30 | 2019-10-01 | Apple Inc. | Method and apparatus for inter process privilige transfer |
US9923896B2 (en) * | 2014-11-24 | 2018-03-20 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Providing access to a restricted resource via a persistent authenticated device network |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4939638A (en) * | 1988-02-23 | 1990-07-03 | Stellar Computer Inc. | Time sliced vector processing |
EP0569195A2 (en) * | 1992-04-30 | 1993-11-10 | Rockwell International Corporation | Telephonic switching system with a user controlled data memory access system and method |
Family Cites Families (123)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4491946A (en) | 1981-03-09 | 1985-01-01 | Gould Inc. | Multi-station token pass communication system |
AU556499B2 (en) | 1981-05-22 | 1986-11-06 | Data General Corporation | Data processing system |
JPH0640302B2 (en) | 1984-01-30 | 1994-05-25 | 株式会社日立製作所 | Schematic / source program automatic generation method |
US4823122A (en) | 1984-06-01 | 1989-04-18 | Digital Equipment Corporation | Local area network for digital data processing system |
US4809160A (en) | 1985-10-28 | 1989-02-28 | Hewlett-Packard Company | Privilege level checking instruction for implementing a secure hierarchical computer system |
US4713806A (en) | 1986-03-14 | 1987-12-15 | American Telephone And Telegraph Company, At&T Bell Laboratories | Communication system control arrangement |
US5287511A (en) | 1988-07-11 | 1994-02-15 | Star Semiconductor Corporation | Architectures and methods for dividing processing tasks into tasks for a programmable real time signal processor and tasks for a decision making microprocessor interfacing therewith |
US4979105A (en) | 1988-07-19 | 1990-12-18 | International Business Machines | Method and apparatus for automatic recovery from excessive spin loops in an N-way multiprocessing system |
US5133075A (en) | 1988-12-19 | 1992-07-21 | Hewlett-Packard Company | Method of monitoring changes in attribute values of object in an object-oriented database |
US5109486A (en) | 1989-01-06 | 1992-04-28 | Motorola, Inc. | Distributed computer system with network and resource status monitoring |
US5088036A (en) | 1989-01-17 | 1992-02-11 | Digital Equipment Corporation | Real time, concurrent garbage collection system and method |
EP0384339B1 (en) | 1989-02-24 | 1997-04-02 | Digital Equipment Corporation | Broker for computer network server selection |
US5297283A (en) | 1989-06-29 | 1994-03-22 | Digital Equipment Corporation | Object transferring system and method in an object based computer operating system |
US5557798A (en) | 1989-07-27 | 1996-09-17 | Tibco, Inc. | Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processes |
US5257369A (en) | 1990-10-22 | 1993-10-26 | Skeen Marion D | Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processes |
US5187787B1 (en) | 1989-07-27 | 1996-05-07 | Teknekron Software Systems Inc | Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processes |
US5218699A (en) | 1989-08-24 | 1993-06-08 | International Business Machines Corporation | Remote procedure calls in heterogeneous systems |
GB2242293A (en) | 1990-01-05 | 1991-09-25 | Apple Computer | Apparatus and method for dynamic linking of computer software components |
AU628753B2 (en) | 1990-08-14 | 1992-09-17 | Digital Equipment Corporation | Method and apparatus for implementing server functions in a distributed heterogeneous environment |
AU639802B2 (en) | 1990-08-14 | 1993-08-05 | Oracle International Corporation | Methods and apparatus for providing dynamic invocation of applications in a distributed heterogeneous environment |
US5446897A (en) | 1990-08-31 | 1995-08-29 | International Business Machines Corporation | Automated address discovery method and apparatus for local area networks |
EP0737921B1 (en) | 1990-09-17 | 2000-06-28 | Cabletron Systems, Inc. | System and method for modelling a computer network |
JPH0799497B2 (en) | 1990-12-14 | 1995-10-25 | インターナショナル・ビジネス・マシーンズ・コーポレイション | Device and method for controlling the use of software |
IE910553A1 (en) | 1991-02-19 | 1992-08-26 | Tolsys Ltd | Improvements in and relating to stable memory circuits |
EP0501610B1 (en) | 1991-02-25 | 1999-03-17 | Hewlett-Packard Company | Object oriented distributed computing system |
EP0501613A3 (en) | 1991-02-28 | 1993-09-01 | Hewlett-Packard Company | Heterogeneous software configuration management apparatus |
US5293614A (en) * | 1991-04-08 | 1994-03-08 | Texas Instruments Incorporated | System and method for hard real-time garbage collection requiring a write barrier but no read barrier |
US5481721A (en) | 1991-07-17 | 1996-01-02 | Next Computer, Inc. | Method for providing automatic and dynamic translation of object oriented programming language-based message passing into operation system message passing using proxy objects |
DE4131380A1 (en) | 1991-09-20 | 1993-03-25 | Siemens Ag | METHOD FOR ADAPTING AN OBJECT-ORIENTED APPLICATION |
US5319751A (en) | 1991-12-27 | 1994-06-07 | Intel Corporation | Device driver configuration in a computer system |
US5826017A (en) | 1992-02-10 | 1998-10-20 | Lucent Technologies | Apparatus and method for communicating data between elements of a distributed system using a general protocol |
US5390328A (en) | 1992-03-30 | 1995-02-14 | International Business Machines Corporation | Data processing system and method for providing notification in a central processor of state changes for shared data structure on external storage |
US5553305A (en) | 1992-04-14 | 1996-09-03 | International Business Machines Corporation | System for synchronizing execution by a processing element of threads within a process using a state indicator |
US5412717A (en) | 1992-05-15 | 1995-05-02 | Fischer; Addison M. | Computer system security method and apparatus having program authorization information data structures |
KR100287045B1 (en) | 1992-07-06 | 2001-04-16 | 존 비. 메이슨 | Method and system for naming/binding object |
JP2524472B2 (en) | 1992-09-21 | 1996-08-14 | インターナショナル・ビジネス・マシーンズ・コーポレイション | How to train a telephone line based speech recognition system |
US5423042A (en) | 1992-10-23 | 1995-06-06 | International Business Machines Corporation | Remote procedure execution |
US5561785A (en) * | 1992-10-29 | 1996-10-01 | International Business Machines Corporation | System for allocating and returning storage and collecting garbage using subpool of available blocks |
EP0669020B1 (en) | 1992-11-13 | 1997-04-02 | Microsoft Corporation | Methods for marshalling interface pointers for remote procedure calls |
US5515536A (en) | 1992-11-13 | 1996-05-07 | Microsoft Corporation | Method and system for invoking methods of an object through a dispatching interface |
US5386568A (en) | 1992-12-01 | 1995-01-31 | Yamaha Corporation | Apparatus and method for linking software modules |
EP0602263A1 (en) | 1992-12-15 | 1994-06-22 | International Business Machines Corporation | User interface program generator |
US5560003A (en) | 1992-12-21 | 1996-09-24 | Iowa State University Research Foundation, Inc. | System and hardware module for incremental real time garbage collection and memory management |
US5452459A (en) | 1993-01-08 | 1995-09-19 | Digital Equipment Corporation | Method and apparatus for allocating server access in a distributed computing environment |
EP0613083B1 (en) | 1993-02-25 | 2002-01-23 | Sun Microsystems, Inc. | Transaction management in object oriented systems |
US5832593A (en) | 1993-04-14 | 1998-11-10 | Minnesota Mining And Manufacturing Company | Splice head for insulated telecommunication wires |
CA2121612A1 (en) | 1993-05-21 | 1994-11-22 | Chung-Hwa Herman Rao | Methods and apparatus for making and using distributed applications |
US5603031A (en) | 1993-07-08 | 1997-02-11 | General Magic, Inc. | System and method for distributed computation based upon the movement, execution, and interaction of processes in a network |
EP0635792B1 (en) | 1993-07-16 | 2003-08-27 | Siemens Aktiengesellschaft | Coordination method for parallel access to resource configurations by a plurality of processors |
US5844553A (en) | 1993-08-30 | 1998-12-01 | Hewlett-Packard Company | Mechanism to control and use window events among applications in concurrent computing |
US5617537A (en) | 1993-10-05 | 1997-04-01 | Nippon Telegraph And Telephone Corporation | Message passing system for distributed shared memory multiprocessor system and message passing method using the same |
CA2118169A1 (en) | 1993-10-27 | 1995-04-28 | Michael R.C. Seaman | Event architecture for system management in an operating system |
US5455952A (en) | 1993-11-03 | 1995-10-03 | Cardinal Vision, Inc. | Method of computing based on networks of dependent objects |
US5742848A (en) | 1993-11-16 | 1998-04-21 | Microsoft Corp. | System for passing messages between source object and target object utilizing generic code in source object to invoke any member function of target object by executing the same instructions |
US5581704A (en) * | 1993-12-06 | 1996-12-03 | Panasonic Technologies, Inc. | System for maintaining data coherency in cache memory by periodically broadcasting invalidation reports from server to client |
US5485617A (en) | 1993-12-13 | 1996-01-16 | Microsoft Corporation | Method and system for dynamically generating object connections |
US5675796A (en) | 1994-04-08 | 1997-10-07 | Microsoft Corporation | Concurrency management component for use by a computer program during the transfer of a message |
US5680617A (en) | 1994-05-16 | 1997-10-21 | Apple Computer, Inc. | Computer-human interface which provides for user customization of object behavior |
EP0684553B1 (en) | 1994-05-26 | 2004-06-16 | Sun Microsystems, Inc. | Method and apparatus for generating and using short operation identifiers in object oriented systems |
US5655148A (en) | 1994-05-27 | 1997-08-05 | Microsoft Corporation | Method for automatically configuring devices including a network adapter without manual intervention and without prior configuration information |
US5680573A (en) * | 1994-07-12 | 1997-10-21 | Sybase, Inc. | Method of buffering data objects in a database |
US5778228A (en) | 1994-08-16 | 1998-07-07 | International Business Machines Corporation | Method and system for transferring remote procedure calls and responses over a network |
US5922054A (en) | 1994-08-19 | 1999-07-13 | Canon Kabushiki Kaisha | System for managing external applications and files |
US5555367A (en) | 1994-09-30 | 1996-09-10 | General Electric Company | Method and system for generating computer programs for queries formed by manipulating object-oriented diagrams |
JP4058118B2 (en) | 1994-11-15 | 2008-03-05 | 株式会社日立製作所 | Program generation system and method |
US5577231A (en) | 1994-12-06 | 1996-11-19 | International Business Machines Corporation | Storage access authorization controls in a computer system using dynamic translation of large addresses |
US5553282A (en) | 1994-12-09 | 1996-09-03 | Taligent, Inc. | Software project history database and method of operation |
US5644768A (en) | 1994-12-09 | 1997-07-01 | Borland International, Inc. | Systems and methods for sharing resources in a multi-user environment |
EP0717337B1 (en) | 1994-12-13 | 2001-08-01 | International Business Machines Corporation | Method and system for the secured distribution of programs |
US5630066A (en) | 1994-12-20 | 1997-05-13 | Sun Microsystems, Inc. | System and method for locating object view and platform independent object |
US5872928A (en) | 1995-02-24 | 1999-02-16 | Cabletron Systems, Inc. | Method and apparatus for defining and enforcing policies for configuration management in communications networks |
US5727203A (en) | 1995-03-31 | 1998-03-10 | Sun Microsystems, Inc. | Methods and apparatus for managing a database in a distributed object operating environment using persistent and transient cache |
US5628005A (en) | 1995-06-07 | 1997-05-06 | Microsoft Corporation | System and method for providing opportunistic file access in a network environment |
US5761656A (en) | 1995-06-26 | 1998-06-02 | Netdynamics, Inc. | Interaction between databases and graphical user interfaces |
US5745703A (en) | 1995-07-18 | 1998-04-28 | Nec Research Institute, Inc. | Transmission of higher-order objects across a network of heterogeneous machines |
US5774551A (en) | 1995-08-07 | 1998-06-30 | Sun Microsystems, Inc. | Pluggable account management interface with unified login and logout and multiple user authentication services |
JPH0962526A (en) | 1995-08-28 | 1997-03-07 | Fujitsu Ltd | Fault resistant rpc system and method therefor |
JP2964926B2 (en) | 1995-08-29 | 1999-10-18 | 富士ゼロックス株式会社 | Database management apparatus and method |
US5671225A (en) | 1995-09-01 | 1997-09-23 | Digital Equipment Corporation | Distributed interactive multimedia service system |
US5737607A (en) | 1995-09-28 | 1998-04-07 | Sun Microsystems, Inc. | Method and apparatus for allowing generic stubs to marshal and unmarshal data in object reference specific data formats |
US5765174A (en) | 1995-10-06 | 1998-06-09 | Sun Microsystems, Inc. | System amd method for distributed object resource management |
US5864862A (en) | 1996-09-30 | 1999-01-26 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method for creating reusable components in an object-oriented programming environment |
US5860153A (en) | 1995-11-22 | 1999-01-12 | Sun Microsystems, Inc. | Memory efficient directory coherency maintenance |
US5692047A (en) | 1995-12-08 | 1997-11-25 | Sun Microsystems, Inc. | System and method for executing verifiable programs with facility for using non-verifiable programs from trusted sources |
US6003763A (en) | 1995-12-29 | 1999-12-21 | Visa International Service | Method and apparatus for recording magnetic information on traveler's checks |
US5745695A (en) | 1996-01-16 | 1998-04-28 | Motorola Inc. | Radio system with suspension of packet data service during non-data service connection |
US5754849A (en) | 1996-01-30 | 1998-05-19 | Wayfarer Communications, Inc. | Self-describing object providing dynamic manipulation of heterogeneous data values and semantic identity between memory and transmission representations |
US5946485A (en) | 1996-02-09 | 1999-08-31 | Intervoice Limited Partnership | Enhanced graphical development environment for controlling program flow |
CA2199108C (en) | 1996-03-05 | 2002-04-23 | Hirotoshi Maegawa | Parallel distributed processing system and method of same |
US5845129A (en) | 1996-03-22 | 1998-12-01 | Philips Electronics North America Corporation | Protection domains in a single address space |
US5790548A (en) | 1996-04-18 | 1998-08-04 | Bell Atlantic Network Services, Inc. | Universal access multimedia data network |
US5815709A (en) | 1996-04-23 | 1998-09-29 | San Microsystems, Inc. | System and method for generating identifiers for uniquely identifying object types for objects used in processing of object-oriented programs and the like |
US6938263B2 (en) | 1996-04-23 | 2005-08-30 | Sun 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 space |
EP0805393B1 (en) | 1996-04-30 | 2011-11-09 | International Business Machines Corporation | Method and apparatus for managing membership of a group of processors in a distributed computing environment |
US5778368A (en) | 1996-05-03 | 1998-07-07 | Telogy Networks, Inc. | Real-time embedded software respository with attribute searching apparatus and method |
US5835737A (en) | 1996-05-10 | 1998-11-10 | Apple Computer, Inc. | Method and apparatus for arbitrating access to selected computer system devices |
US5928323A (en) | 1996-05-30 | 1999-07-27 | Sun Microsystems, Inc. | Apparatus and method for dynamically generating information with server-side software objects |
US5813013A (en) | 1996-06-06 | 1998-09-22 | Microsoft Corporation | Representing recurring events |
US5768532A (en) | 1996-06-17 | 1998-06-16 | International Business Machines Corporation | Method and distributed database file system for implementing self-describing distributed file objects |
JP3488019B2 (en) | 1996-06-17 | 2004-01-19 | 株式会社山武 | How to reuse parts of configuration tool for control design |
US5991823A (en) | 1996-06-26 | 1999-11-23 | Sun Microsystems, Inc. | Low overhead object adaptor |
US6044409A (en) | 1996-06-26 | 2000-03-28 | Sun Microsystems, Inc. | Framework for marshaling and unmarshaling argument object references |
US5727145A (en) | 1996-06-26 | 1998-03-10 | Sun Microsystems, Inc. | Mechanism for locating objects in a secure fashion |
US5809507A (en) | 1996-07-01 | 1998-09-15 | Sun Microsystems, Inc. | Method and apparatus for storing persistent objects on a distributed object network using a marshaling framework |
US6360256B1 (en) | 1996-07-01 | 2002-03-19 | Sun Microsystems, Inc. | Name service for a redundant array of internet servers |
US5860004A (en) | 1996-07-03 | 1999-01-12 | Sun Microsystems, Inc. | Code generator for applications in distributed object systems |
US5757925A (en) | 1996-07-23 | 1998-05-26 | Faybishenko; Yaroslav | Secure platform independent cross-platform remote execution computer system and method |
US5875335A (en) | 1996-09-30 | 1999-02-23 | Apple Computer, Inc. | Parameter marshaling techniques for dynamic object-oriented programming languages |
US5787425A (en) | 1996-10-01 | 1998-07-28 | International Business Machines Corporation | Object-oriented data mining framework mechanism |
US5832529A (en) | 1996-10-11 | 1998-11-03 | Sun Microsystems, Inc. | Methods, apparatus, and product for distributed garbage collection |
US5892904A (en) | 1996-12-06 | 1999-04-06 | Microsoft Corporation | Code certification for network transmission |
US5884024A (en) | 1996-12-09 | 1999-03-16 | Sun Microsystems, Inc. | Secure DHCP server |
US5787431A (en) | 1996-12-16 | 1998-07-28 | Borland International, Inc. | Database development system with methods for java-string reference lookups of column names |
US5815149A (en) | 1997-02-19 | 1998-09-29 | Unisys Corp. | Method for generating code for modifying existing event routines for controls on a form |
US5935249A (en) | 1997-02-26 | 1999-08-10 | Sun Microsystems, Inc. | Mechanism for embedding network based control systems in a local network interface device |
US6061713A (en) | 1997-03-12 | 2000-05-09 | Fujitsu Limited | Communications system for client-server data processing systems |
US5864866A (en) | 1997-03-26 | 1999-01-26 | International Business Machines Corporation | Apparatus and method for providing externalization in an object-oriented environment |
US5890158A (en) | 1997-03-31 | 1999-03-30 | International Business Machines Corporation | Method, apparatus, and program storage device for sharing objects with a network server and a database server using a common object model |
US5878411A (en) | 1997-06-27 | 1999-03-02 | International Business Machines Corporation | Dependent object class and subclass mapping to relational data store |
US5887134A (en) | 1997-06-30 | 1999-03-23 | Sun Microsystems | System and method for preserving message order while employing both programmed I/O and DMA operations |
US5946694A (en) | 1997-09-29 | 1999-08-31 | International Business Machines Corporation | Apparatus and method for transparent application of service to business objects |
US6061699A (en) | 1997-11-03 | 2000-05-09 | International Business Machines Corporation | Method and computer program product for extracting translatable material from browser program function codes using variables for displaying MRI |
US6009103A (en) | 1997-12-23 | 1999-12-28 | Mediaone Group, Inc. | Method and system for automatic allocation of resources in a network |
-
1998
- 1998-03-20 US US09/044,838 patent/US6247026B1/en not_active Expired - Lifetime
-
1999
- 1999-02-17 CN CN99805396A patent/CN1298509A/en active Pending
- 1999-02-17 EP EP99936130A patent/EP1062580A1/en not_active Withdrawn
- 1999-02-17 KR KR1020007009396A patent/KR20010041296A/en not_active Application Discontinuation
- 1999-02-17 AU AU32972/99A patent/AU3297299A/en not_active Abandoned
- 1999-02-17 JP JP2000533814A patent/JP2002505470A/en active Pending
- 1999-02-17 WO PCT/US1999/003400 patent/WO1999044130A1/en not_active Application Discontinuation
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4939638A (en) * | 1988-02-23 | 1990-07-03 | Stellar Computer Inc. | Time sliced vector processing |
EP0569195A2 (en) * | 1992-04-30 | 1993-11-10 | Rockwell International Corporation | Telephonic switching system with a user controlled data memory access system and method |
Non-Patent Citations (1)
Title |
---|
ANONYMOUS: "Resource Preemption for Priority Scheduling. November 1973.", IBM TECHNICAL DISCLOSURE BULLETIN, vol. 16, no. 6, New York, US, pages 1931, XP002109435 * |
Cited By (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2005013157A2 (en) | 2003-08-01 | 2005-02-10 | Oracle International Corporation | Dynamic reassignment of data ownership |
WO2005013157A3 (en) * | 2003-08-01 | 2005-11-03 | Oracle Int Corp | Dynamic reassignment of data ownership |
US7120651B2 (en) | 2003-08-01 | 2006-10-10 | Oracle International Corporation | Maintaining a shared cache that has partitions allocated among multiple nodes and a data-to-partition mapping |
US7139772B2 (en) | 2003-08-01 | 2006-11-21 | Oracle International Corporation | Ownership reassignment in a shared-nothing database system |
US7277897B2 (en) | 2003-08-01 | 2007-10-02 | Oracle International Corporation | Dynamic reassignment of data ownership |
US8234517B2 (en) | 2003-08-01 | 2012-07-31 | Oracle International Corporation | Parallel recovery by non-failed nodes |
WO2013122977A1 (en) * | 2012-02-16 | 2013-08-22 | Citrix Systems, Inc. | Connection leasing for hosted services |
US8990898B2 (en) | 2012-02-16 | 2015-03-24 | Citrix Systems, Inc. | Connection leasing for hosted services |
US9426227B2 (en) | 2012-02-16 | 2016-08-23 | Citrix Systems, Inc. | Connection leasing for hosted services |
US9800669B2 (en) | 2012-02-16 | 2017-10-24 | Citrix Systems, Inc. | Connection leasing for hosted services |
US10839116B2 (en) | 2016-08-24 | 2020-11-17 | Improbable Worlds Ltd | Simulation systems and methods |
US10303821B2 (en) | 2016-08-24 | 2019-05-28 | Improbable Worlds Ltd. | Load balancing systems and methods for spatially-optimized simulations |
US10380282B2 (en) | 2016-08-24 | 2019-08-13 | Improbable Worlds Ltd | Distributable and customizable load-balancing of data-associated computation via partitions and virtual processes |
US10579434B2 (en) | 2016-08-24 | 2020-03-03 | Improbable Worlds Ltd | Simulation systems and methods using query-based interest |
US10643010B2 (en) | 2016-08-24 | 2020-05-05 | Improbable Worlds Ltd | Scalable simulation system with scalable data propagation |
US10878146B2 (en) | 2016-08-24 | 2020-12-29 | Improbable Worlds Ltd | Handover techniques for simulation systems and methods |
US11087047B2 (en) | 2016-08-24 | 2021-08-10 | Improbable Worlds Ltd | Scalable update propagation via query aggregations and connection migrations |
US11416305B2 (en) | 2016-08-24 | 2022-08-16 | Improbable Worlds Limited | Commands for simulation systems and methods |
US11533367B2 (en) | 2016-08-24 | 2022-12-20 | Improbable Worlds Ltd | Simulation systems and methods using query-based interest |
US11550621B2 (en) | 2016-08-24 | 2023-01-10 | Improbable Worlds Ltd | Distributable and customizable load-balancing of data-associated computation via partitions and virtual processes |
US11816402B2 (en) | 2016-08-24 | 2023-11-14 | Improbable Worlds Limited | Simulation systems and methods |
US11936734B2 (en) | 2016-08-24 | 2024-03-19 | Improbable Worlds Ltd | Simulation systems and methods using query-based interest |
WO2019081911A1 (en) * | 2017-10-27 | 2019-05-02 | Improbable Worlds Ltd. | Handover techniques for simulation systems and methods |
Also Published As
Publication number | Publication date |
---|---|
EP1062580A1 (en) | 2000-12-27 |
JP2002505470A (en) | 2002-02-19 |
KR20010041296A (en) | 2001-05-15 |
AU3297299A (en) | 1999-09-15 |
CN1298509A (en) | 2001-06-06 |
US6247026B1 (en) | 2001-06-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6247026B1 (en) | Method, apparatus, and product for leasing of delegation certificates in a distributed system | |
US6263350B1 (en) | Method and system for leasing storage | |
US6421704B1 (en) | Method, apparatus, and product for leasing of group membership in a distributed system | |
US6499049B2 (en) | Lease renewal service | |
US6728737B2 (en) | Method and system for leasing storage | |
EP1057105B1 (en) | Method and system for leasing storage | |
EP1057106B1 (en) | Method, apparatus, and product for leasing of group membership in a distributed system | |
WO1999044128A1 (en) | Leasing for failure detection | |
KR20010041228A (en) | Method and system for leasing storage | |
CLEAN | 1 BEGIN |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 99805396.1 Country of ref document: CN |
|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG UZ VN YU ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW SD SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 1020007009396 Country of ref document: KR |
|
ENP | Entry into the national phase |
Ref document number: 2000 533814 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1999936130 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 1999936130 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWP | Wipo information: published in national office |
Ref document number: 1020007009396 Country of ref document: KR |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 1020007009396 Country of ref document: KR |