System and method for the synchronization of a file in a cache

• US 8,117,152 B2
• Filed: 08/21/2009
• Issued: 02/14/2012
• Est. Priority Date: 12/28/2001
• Status: Expired due to Term

• Current Assignee: Ip Ot Sub Ulc
• Original Assignee: Open TEXT SA (Open Text Corporation)
• Inventors: Thomas, David, Wells, Scott
• Primary Examiner(s): LEWIS, CHERYL RENEA
• Application Number:
  US12/545,423
• Publication Number:
  US 20100049757A1
• Time in Patent Office: 907 Days
• Field of Search: 707/609, 709/203
• US Class Current: 707/609
• CPC Class Codes: G06F 12/0804 with main memory updating G06F12/0806 takes precedence
• CPC Class Codes: G06F 12/0866 for peripheral storage systems, e.g. disk cache
• CPC Class Codes: G06F 16/168 Details of user interfaces specifically adapted to file systems, e.g. browsing and visualisation, 2d or 3d GUIs query results presentation G06F16/156
• CPC Class Codes: G06F 16/172 Caching, prefetching or hoarding of files
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 16/184 implemented as replicated file system
• CPC Class Codes: G06F 2212/1024 Latency reduction
• CPC Class Codes: G06F 2212/154 Networked environment
• CPC Class Codes: G06F 2212/163 Server or database system
• CPC Class Codes: G06F 2212/263 Network storage, e.g. SAN or NAS
• CPC Class Codes: G06F 2212/264 Remote server
• CPC Class Codes: G06F 2212/463 File
• CPC Class Codes: G06F 3/0482 Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G06F 3/04842 Selection of displayed objects or displayed text elements G06F3/0482 takes precedence
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: Y10S 707/951 Calendar or scheduling
• CPC Class Codes: Y10S 707/959 Network
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users

Abstract

The present invention provides a system and method of synchronizing a cache that substantially eliminates or reduces disadvantages associated with previously developed systems and methods of synchronizing caches. More particularly, embodiments of the present invention provide a system and method for bi-directional synchronization of a cache. One embodiment of the system of this invention includes a software program stored on a computer readable medium. The software program can be executed by a computer processor to run in user space and perform steps comprising: receiving a database asset from a database; storing the database asset as a cached file in a cache; determining if the cached file has been modified; and if the cached file has been modified, communicate the cached file directly to the database. In one embodiment of the present invention, the software program can determine if the cached file has been modified through automatic notification from a file management system. Alternatively, the software program can poll a cached file to determine if the cached file has changed. In another embodiment of the present invention, the software program can be further executable to perform the step of prompting an operating system to open the cached file in an application associated with the cached file'"'"'s file type. In yet another embodiment of the present invention, the software program can be further executable to receive notifications from a database of when contention for a database asset occurs. Thus, bi-directional synchronization can occur.

Claims

1. A method for synchronizing a file in a cache comprising:

a cache manager at a client computer receiving a database asset from a database at a database server, wherein the client computer is executing an operating system, the cache manager, and a local application, wherein the client computer is coupled to the database server over a network;

the cache manager storing the database asset in a cache of the client computer as a cached file;

the cache manager prompting the operating system to open the cached file using a local application associated with a file type for the cached file;

receiving, at the cache manager, a notification from the operating system indicating that the cached file has been modified;

the cache manager determining that the cached file has been modified based on receiving the notification from the operating system; and

the cache manager communicating the modified cached file to the database.

2. The method of claim 1, further comprising:

prior to said receiving at the client computer the database asset, the cache manager requesting the database asset from the database.

3. The method of claim 2, further comprising:

the cache manager establishing the connection with the database, wherein the database server is executing a database management application managing the database;

the cache manager determining if the connection with the database has become disconnected; and

if the connection with the database has become disconnected, the cache manager reestablishing the connection to the database.

4. The method of claim 1, further comprising:

the cache manager associating the cached file with a connection.

5. The method of claim 1, further comprising:

the cache manager associating the cached file with a location in a memory.

6. The method of claim 1, further comprising:

the cache manager notifying a first user that an additional user has accessed the database asset.

7. The method of claim 1, further comprising:

the cache manager purging the cached file from the cache if the database asset is deleted from the database.

8. A non-transitory computer readable storage medium including computer executable program instructions for:

connecting a client computer executing an operating system, a cache manager and a local application to a database server;

receiving, at the client computer, a database asset from a database at a database server;

storing the database asset in a cache as a cached file in a computer readable memory of the client computer using a cache manager;

causing the cache manager to prompt the operating system to open the cached file using a local application associated with a file type for the cached file;

causing the cache manager to determine if the cached file has been modified based on a notification from a file management system of the operating system; and

if the cached file has been modified, communicating the cached file to the database.

9. The non-transitory computer readable storage medium of claim 8, further comprising computer program instructions for:

prior to said receiving at the client computer the database asset, requesting the database asset from the database.

10. The non-transitory computer program product of claim 8, further comprising computer executable program instructions for:

associating the cached file with a connection.

11. The non-transitory computer program product of claim 10, further comprising computer executable program instructions for:

establishing the connection with the database, wherein the database is managed by a database management program;

determining if the connection with the database has become disconnected; and

if the connection with the database has become disconnected, reestablishing the connection to the database.

12. The non-transitory computer program product of claim 10, further comprising computer executable program instructions for:

associating the cached file with a location in a memory.

13. The non-transitory computer program product of claim 10, further comprising computer executable program instructions for:

notifying a first user that an additional user has accessed the database asset.

14. The non-transitory computer program product of claim 10, further comprising computer executable program instructions for:

purging the cached file from the cache if the database asset is deleted from the database.

15. A system comprising:

a database server computer coupled to a network, wherein the database server computer includes a database, wherein the database server computer is executing a database management application managing the database; and

a client computer coupled to the database server computer via the network, wherein the client computer comprises a cache, wherein the client computer is executing an operating system, a cache manager, and a local application, wherein the cache manager manages the cache, wherein the cache manager is operable to;

receive a database asset from a database at a database server;

store the database asset in a cache of the client computer as a cached file;

prompt the operating system to open the cached file using a local application associated with a file type for the cached file;

receive a notification from the operating system indicating that the cached file has been modified;

determine that the cached file has been modified based on receiving the notification from the operating system; and

communicate the modified cached file to the database.

16. The system of claim 15, wherein the cache manager is further operable to:

prior to receiving the database asset, request the database asset from the database.

17. The system of claim 15, wherein the cache manager is further operable to:

associate the cached file with a connection.

18. The system of claim 17, wherein the cache manager is further operable to:

establish the connection with the database;

determine if the connection with the database has become disconnected; and

if the connection with the database has become disconnected, reestablish the connection to the database.

19. The system of claim 15, wherein the cache manager is further operable to:

associate the cached file with a location in a memory.

20. The system of claim 15, wherein the cache manager is further operable to:

notify a first user that an additional user has accessed the database asset.