System and method for processing resource registry updates without regard to chronological order

• US 20050149615A1
• Filed: 12/17/2003
• Published: 07/07/2005
• Est. Priority Date: 12/17/2003
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Lee, Steven J., Nedimyer, Joseph P., Rowe, Billy R. Jr.
• Application Number:
  US10/738,482
• Publication Number:
  US 20050149615A1
• Time in Patent Office: Days
• US Class Current: 709/202
• CPC Class Codes: G06F 16/2322 using timestamps

Abstract

The processing of management messages controlling resources and links in a resource repository may occur without regard to chronological order of the message creation. Resources and links include at least one timestamp, and a delete pending indicator. Messages to add, modify, and delete resources and links include a message timestamp. The management messages are conditionally processed based on a comparison between the message timestamp and the resource/link timestamp(s) and delete pending indicator. In an exemplary embodiment, AddResource, ModifyResource, DeleteResource, AddLink and DeleteLink messages are defined and their conditional processing described.

Claims

1. A method of managing resources and bidirectional links between said resources in a resource repository, comprising:

(1) collecting and updating information regarding entities represented by said resources via a plurality of agents;

(2) accessing said resource repository by said agents; and

(3) conditionally adding, modifying, or deleting said resources and/or links by said agents without regard to chronological order, in response to timestamps associated with said resources and links.

2. The method of claim 1 wherein conditionally adding, modifying, and deleting said resources and links comprises conditionally processing resource repository messages, each said message including a message timestamp.

3. The method of claim 2 wherein conditionally processing resource repository messages comprises processing said messages if said message timestamp exceeds said resource or link timestamp, and not processing said messages if said message timestamp does not exceed said resource or link timestamp.

4. The method of claim 3 wherein processing said messages if said message timestamp exceeds said resource or link timestamp includes updating said resource or link timestamp to said message timestamp value.

5. The method of claim 2 wherein each said resource and link in said repository includes a modification timestamp and a deletion timestamp.

6. The method of claim 5 wherein each said resource and link in said repository additionally includes a delete pending indicator.

7. The method of claim 6 wherein conditionally deleting each said resource or link comprises, if the resource or link delete pending indicator is false and if the delete message timestamp exceeds the resource or link modification timestamp, setting the delete pending indicator to true and updating the deletion timestamp of the resource or link to the value of the delete message timestamp.

8. The method of claim 7 further comprising periodically performing a garbage collection operation wherein resources and links whose delete pending indicators are true are removed from said resource repository.

9. The method of claim 1 wherein conditionally adding a link includes conditionally adding a resource as an endpoint of said link if said resource does not exist in said repository.

10. The method of claim 1 wherein conditionally deleting a resource includes conditionally deleting each link associated with said resource.

11. A method of processing, without regard to chronological order, an AddResource or ModifyResource message having a message timestamp and resource attributes, in a resource repository including resources and bidirectional links between said resources, said resources and links having attributes, at least one timestamp and a delete pending indicator, comprising:

(1) determining if the resource referenced by said AddResource/ModifyResource message is already in said repository;

(A) if said resource is already in said repository, and if said message timestamp exceeds a timestamp of said resource;

(i) transferring said resource attributes from said message to said resource;

(ii) setting a timestamp of said resource to said message timestamp value; and

(iii) if the delete indicator of said resource is true,

(a) setting said delete pending indicator to false;

(B) if said resource is not already in said repository;

(i) creating a new resource in said repository having the resource attributes of said message; and

(ii) setting a timestamp of said resource to said message timestamp value.

12. A method of processing, without regard to chronological order, a DeleteResource message having a message timestamp and resource attributes, in a resource repository including resources and bidirectional links between said resources, said resources and links having attributes, at least one timestamp and a delete pending indicator, comprising:

(1) determining if the resource referenced by said DeleteResource message is in said repository;

(A) if said resource is in said repository, and if said message timestamp exceeds a timestamp of said resource;

(i) setting a timestamp of said resource to said message timestamp value;

(ii) if the delete pending indicator of said resource is false;

(a) setting said delete pending indicator to true; and

(b) processing all links associated with said resource;

(B) if said resource is not in said repository,

(i) creating a shell resource in said repository;

(ii) setting a timestamp of said shell resource to said message timestamp value; and

(iii) setting the delete pending indicator of said shell resource to true.

13. The method of claim 12, wherein processing links associated with said resource comprises, for each said link:

(1) if said message timestamp exceeds a timestamp of said link;

(A) setting a timestamp of said link to said message timestamp value; and

(B) if the delete pending indicator of said link is false,

(i) setting the delete pending indicator of said link to true;

(2) if said message timestamp is less than a timestamp of said link and the delete pending indicator of said link is false,

(A) setting the delete pending indicator of the said resource to true.

14. The method of claim 13, further comprising periodically performing a garbage collection operation wherein resources and links whose delete pending indicators are true are removed from said resource repository.

15. A method of processing, without regard to chronological order, an AddLink message having a message timestamp and link attributes, in a resource repository including resources and bidirectional links between said resources, said resources and links having attributes, at least one timestamp and a delete pending indicator, comprising:

(1) determining if the link referenced by said AddLink message is already in said repository;

(A) if said resource is not in said repository, creating a link in said repository with a timestamp having the value of said message timestamp;

(2) if said message timestamp exceeds a link timestamp;

(B) setting a timestamp of said link to said message timestamp value;

(3) determining the resources associated with said link; and

(4) processing said resources.

16. The method of claim 15, wherein processing said resources comprises, for each said resource associated with said link:

(1) if said resource does not exists in said repository;

(A) creating a resource in said repository with a timestamp having the value of said message timestamp;

(2) if said message timestamp exceeds a resource timestamp

(A) setting a timestamp of said resource to said message timestamp value;

(B) if a delete pending indicator of said resource is true;

(i) setting said delete pending indicator to false.

17. A method of processing, without regard to chronological order, a DeleteLink message having a message timestamp and link attributes, in a resource repository including resources and bidirectional links between said resources, said resources and links having attributes, at least one timestamp and a delete pending indicator, comprising:

(1) determining if the link referenced by said DeleteLink message is in said repository;

(A) if said link is in said repository, and if said message timestamp exceeds a timestamp of said link;

(i) setting a timestamp of said link to said message timestamp value;

(ii) if the delete pending indicator of said link is false;

(a) setting said delete pending indicator to true;

(B) if said link is not in said repository,

(i) creating a link in said repository;

(ii) setting a timestamp of said link to said message timestamp value; and

(iii) setting the delete pending indicator of said link to true.