Transaction-aware caching for access control metadata

• US 7,203,709 B2
• Filed: 05/30/2003
• Issued: 04/10/2007
• Est. Priority Date: 05/12/2000
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Pitfield, David B., Long, David J.
• Primary Examiner(s): Gaffin; Jeffrey
• Assistant Examiner(s): STACE, BRENT S
• Application Number:
  US10/452,164
• Publication Number:
  US 20030195866A1
• Time in Patent Office: 1,411 Days
• Field of Search: 707/1, 707/8, 707/100, 707/103.R, 707/203, 707/201, 707/200
• US Class Current: 1/1
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

Techniques are provided for performing transaction-aware caching of metadata in an electronic file system. A mechanism is described for providing transaction-aware caching that uses a cache hierarchy, where the cache hierarchy includes uncommitted caches associated with sessions in an application and a committed cache that is shared among the sessions in that application. Techniques are described for caching document metadata, access control metadata and folder path metadata. Also described is a technique for using negative cache entries to avoid unnecessary communications with a server when applications repeatedly request non-existent data.

Claims

1. A computer implemented method for maintaining folder path metadata for a file in a cache hierarchy comprising the steps of:

storing within a first cache a first version of said folder path metadata that includes only changes made by a transaction associated with said first cache;

storing within a second cache a second version of said folder path metadata that does not include said changes made by said transaction;

storing within a third cache folder path metadata that includes only changes made by a transaction associated with said third cache;

providing data from said first version of said folder path metadata to said transaction associated with said first cache;

providing data from said second version of said folder path metadata to transactions other than said transaction until said transaction associated with said first cache successfully terminates;

maintaining folder path metadata by invalidating said second version of said folder path metadata when said transaction associated with said first cache successfully terminates;

receiving a request for an operation related to a file stored in a database system;

processing said request by;

looking in said first cache for particular folder path metadata associated with said file and responding to the request if said first cache has said particular folder path metadata associated with said file; and

if said first cache does not have said particular folder path metadata associated with said file, then

looking in said second cache for said particular folder path metadata associated with said file and responding to the request if said second cache has said particular folder path metadata associated with said file, wherein said second cache only contains folder path metadata that has been committed by the database.

2. The method of claim 1, wherein said first cache and said second cache reside external to any database server that belongs to a database system that manages the file.

3. A computer implemented method for looking for folder path metadata comprising the steps of:

maintaining outside of a database system a first cache and a second cache that concurrently store said folder path metadata for files stored in said database system;

wherein said first cache stores a first set of folder path metadata that reflects modifications made during a first session and does not reflect modifications made during a second session;

wherein said second cache stores a second set of folder path metadata that reflects said modifications made during said second session and does not reflect said modifications made during said first session;

providing requests received in said first session with data from said first set of folder path metadata;

providing requests received in said second session with data from said second set of folder path metadata;

receiving a request associated with said first session for an operation related to a file stored in the database system;

processing said request by;

looking in said first cache for particular folder path metadata associated with said file and responding to the request associated with said first session if said first cache has said particular folder path metadata associated with said file; and

if said first cache does not have said particular folder path metadata associated with said file, then

looking in a third cache for said particular folder path metadata associated with said file and responding to the request associated with said first session if said third cache has said particular folder path metadata associated with said file,

wherein said third cache only contains folder path metadata that has been committed by the database.

4. The method of claim 3 wherein the step of providing requests received in said first session further comprises the step of:

inspecting tokens of said folder path metadata one at a time.

5. The method of claim 3 wherein a particular request results in a reference to unmodified metadata for a particular token and wherein said method further comprises the step of:

placing an identifier for said particular token into said third cache.

6. The method of claim 5 wherein the step of placing said identifier further comprises the step of:

placing said identifier into an identifier column.

7. The method of claim 3 wherein a particular request results in a reference to an unmodified child token and wherein said method further comprises the step of:

placing said child token into said third cache.

8. The method of claim 7 wherein the step of placing said child token further comprises the step of:

placing said child token into a metadata column of said third cache.

9. The method of claim 3 wherein a particular request results in a reference to a child token associated with a particular token with modified metadata and wherein said method further comprises the step of:

placing said child token into said first cache.

10. The method of claim 9 wherein the step of placing said child token further comprises the step of:

placing said child token in a metadata column of said first cache.

11. The method of claim 3 a particular request results in a reference to a child token associated with a particular token with modified metadata and wherein said method further comprises the step of:

placing an identifier for said particular token into said first cache.

12. The method of claim 3 wherein the step of looking for said folder path metadata in said first cache further comprises the steps of:

determining an identifier from said folder path metadata in said first cache; and

retrieving a file from said database system using said identifier.

13. The method of claim 3 wherein the step of looking for said folder path metadata in said third cache further comprises the steps of:

determining an identifier from said folder path metadata in said third cache; and

retrieving a file from said database system using said identifier.

14. The method of claim 3 wherein said first cache contains previously modified folder path metadata and wherein said method further comprises the step of:

posting a commit event for all tokens in said previously modified folder path metadata to said second cache.

15. The method of claim 14 further comprising the steps of:

receiving at said second cache said commit event for a particular token; and

marking said particular token invalid in said second cache.

16. The method of claim 3 further comprising the step of sending a request for said particular folder path metadata to said database system if said particular folder path metadata is not in said third cache.