Systems and methods for caching of managed content in a distributed environment using a multi-tiered architecture

• US 10,021,209 B2
• Filed: 04/08/2016
• Issued: 07/10/2018
• Est. Priority Date: 04/10/2015
• Status: Active Grant

• Current Assignee: Open Text Sa Ulc (Open Text Corporation)
• Original Assignee: Open Text Sa Ulc (Open Text Corporation)
• Inventors: Ionescu, Nicolae, Trufasiu, Dan-Horia, Varga, Peter, Zhou, Tao, Pauthner, Franz, Wong, Yue Kuk
• Primary Examiner(s): Williams, Clayton R
• Application Number:
  US15/094,524
• Publication Number:
  US 20160301766A1
• Time in Patent Office: 823 Days
• CPC Class Codes: G06F 16/172 Caching, prefetching or hoarding of files
• CPC Class Codes: G06F 16/173 Customisation support for file systems, e.g. localisation, multi-language support, personalisation
• CPC Class Codes: G06F 16/2329 using versioning
• CPC Class Codes: G06F 16/2474 Sequence data queries, e.g. querying versioned data
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

Embodiments as disclosed provide a distributed caching solution that improve the performance and functionality of a content management platform for sites that are physically or logically remote from the primary site of the content management platform. In particular, according to embodiments, a remote cache server may be associated with a remote site to store local copies of documents that are managed by the primary content management platform. Periodically, a portion of the remote site'"'"'s cache may be synchronized with the content management platform'"'"'s primary site using an extensible architecture to ensure that content at the remote cache server is current.

Claims

1. A system for remote caching, comprising:

a primary content management server for managing content;

a remote cache system, including;

a processor;

a cache;

an interface to a network;

a data store for storing metadata corresponding to content stored in the cache, wherein the content in cache is managed by the primary content management server; and

a remote client transfer module for;

receiving a first request to access content, wherein the first request is associated with a user;

accessing the data store to determine if first metadata associated with the requested content is stored in the data store;

sending a second request to a primary content transfer module associated with the primary content management server based on a presence of first metadata associated with the requested content;

receiving a first response from the primary content transfer module including second metadata;

comparing the first metadata to the second metadata to determine if a version of the content stored in the cache is a current version of the content;

if the version of the content stored in the cache is a current version, providing the content in the cache in response to the first request;

if the version of the content stored in the cache is not the current version,

sending a third request for the current version of the content to the primary content transfer module;

receiving the current version of the content;

storing the current version of the content in the cache; and

providing the content in the cache in response to the first request; and

the primary content transfer module for;

receiving the second request associated with the content from the remote client transfer module;

sending a fourth request to the primary content management server for the second metadata associated with the content;

determining if the user has permission to access the content based on the second metadata and the second request

if the user does not have permission returning a response indicating the user does not have permission;

if the user does have permission,

 

returning the first response, including the second metadata to the remote client transfer module;

 

receiving the third request for the current version of the content;

 

obtaining the current version of the content from a content management platform; and

 

returning the current version of the content to the remote client transfer module.

2. The remote caching system of claim 1, wherein the third request is a single request.

3. The remote caching system of claim 2, wherein the first request is received from one of a set of cache module clients, each cache module client corresponding to a type of repository platform application.

4. The remote caching system of claim 2, wherein the primary content transfer module is further for determining a location of the requested content based on the second metadata and if the location is not the primary content management server forming a resource locator associated with the current version of the requested content and returning the first response including the resource locator for the current version of the requested content and the second metadata, and

wherein the remote cache transfer module is further adapted to obtain the current version of the requested content from the location using the resource locator and store the current version of the requested content in the cache.

5. The remote caching system of claim 4, wherein the location is a repository platform.

6. The remote caching system of claim 5, wherein the repository platform is a different type of platform from the primary content management server.

7. The remote caching system of claim 2, wherein the remote client transfer module is further for:

receiving a fifth request to save content from the user,

updating metadata associated with the saved content in the data store;

updating the saved content in the cache;

sending a second response to the user indicating the content has been saved; and

subsequently to sending the second response to the user, sending a sixth request to the primary content management server to save the saved content at the primary content management server.

8. The remote caching system of claim 1, wherein the remote client transfer module is further for:

receiving a fifth request to access content, wherein the fifth request is associated with the user;

sending a sixth request to the primary content transfer module associated with the requested content;

determining that the primary content transfer module is inaccessible over the network;

accessing the data store to determine if the requested content is in the cache; and

providing the content in the cache in response to the fifth request.

9. A method for remote caching, comprising:

receiving, at a remote client transfer module of a system including a primary content management server for managing content, a remote cache system including a cache storing content managed by the primary content management server and a data store for storing metadata corresponding to content stored in the cache, a first request to access content, wherein the first request is associated with a user;

accessing the data store to determine if first metadata associated with the requested content is stored in the data store;

sending a second request to a primary content transfer module associated with the primary content management server based on a presence of first metadata associated with the requested content;

receiving a first response from the primary content transfer module including second metadata;

comparing the first metadata to the second metadata to determine if a version of the content stored in the cache is a current version of the content;

if the version of the content stored in the cache is a current version, providing the content in the cache in response to the first request;

if the version of the content stored in the cache is not the current version,

sending a third request for the current version of the content to the primary content transfer module;

receiving the current version of the content;

storing the current version of the content in the cache; and

providing the content in the cache in response to the first request; and

receiving, by the primary content transfer module, the second request associated with the content from the remote client transfer module;

sending a fourth request to the primary content management server for the second metadata associated with the content;

determining if the user has permission to access the content based on the second metadata and the second request

if the user does not have permission returning a response indicating the user does not have permission;

if the user does have permission,

returning the first response, including the second metadata to the remote client transfer module;

receiving the third request for the current version of the content;

obtaining the current version of the content from a content management platform; and

returning the current version of the content to the remote client transfer module.

10. The method of claim 9, wherein the third request is a single request.

11. The method of claim 10, wherein the first request is received from one of a set of cache module clients, each cache module client corresponding to a type of repository platform application.

12. The method of claim 10, wherein the primary content transfer module is further for determining a location of the requested content based on the second metadata and if the location is not the primary content management server forming a resource locator associated with the current version of the requested content and returning the first response including the resource locator for the current version of the requested content and the second metadata, and

wherein the remote cache transfer module is further adapted to obtain the current version of the requested content from the location using the resource locator and store the current version of the requested content in the cache.

13. The method of claim 12, wherein the location is a repository platform.

14. The method of claim 13, wherein the repository platform is a different type of platform from the primary content management server.

15. The method of claim 10, wherein the remote client transfer module is further for:

receiving a fifth request to save content from the user,

updating metadata associated with the saved content in the data store;

updating the saved content in the cache;

sending a second response to the user indicating the content has been saved; and

subsequently to sending the second response to the user, sending a sixth request to the primary content management server to save the saved content at the primary content management server.

16. A non-transitory computer readable medium, comprising instruction for implementing remote caching in a system including a primary content management server for managing content, a remote cache system including a cache and a data store for storing metadata corresponding to content stored in the cache, where the content in cache is managed by the primary content management server, the instruction translatable to implement a remote client transfer module and a primary content transfer module, and

at the remote client transfer module:

receiving a first request to access content, wherein the first request is associated with a user;

accessing the data store to determine if first metadata associated with the requested content is stored in the data store;

sending a second request to a primary content transfer module associated with the primary content management server based on a presence of first metadata associated with the requested content;

receiving a first response from the primary content transfer module including second metadata;

comparing the first metadata to the second metadata to determine if a version of the content stored in the cache is a current version of the content;

if the version of the content stored in the cache is a current version, providing the content in the cache in response to the first request;

if the version of the content stored in the cache is not the current version,

sending a third request for the current version of the content to the primary content transfer module;

receiving the current version of the content;

storing the current version of the content in the cache; and

providing the content in the cache in response to the first request; and

at the primary content transfer module;

receiving the second request associated with the content from the remote client transfer module;

sending a fourth request to the primary content management server for the second metadata associated with the content;

determining if the user has permission to access the content based on the second metadata and the second request

if the user does not have permission returning a response indicating the user does not have permission;

if the user does have permission,

returning the first response, including the second metadata to the remote client transfer module;

receiving the third request for the current version of the content;

obtaining the current version of the content from a content management platform; and

returning the current version of the content to the remote client transfer module.

17. The computer readable medium of claim 16, wherein the third request is a single request.

18. The computer readable medium of claim 17, wherein the first request is received from one of a set of cache module clients, each cache module client corresponding to a type of repository platform application.

19. The computer readable medium of claim 17, wherein the primary content transfer module is further for determining a location of the requested content based on the second metadata and if the location is not the primary content management server forming a resource locator associated with the current version of the requested content and returning the first response including the resource locator for the current version of the requested content and the second metadata, and

wherein the remote cache transfer module is further adapted to obtain the current version of the requested content from the location using the resource locator and store the current version of the requested content in the cache.

20. The computer readable medium of claim 19, wherein the location is a repository platform.

21. The computer readable medium of claim 20, wherein the repository platform is a different type of platform from the primary content management server.

22. The computer readable medium of claim 17, wherein the instructions for the remote client transfer module are further for:

receiving a fifth request to save content from the user, updating metadata associated with the saved content in the data store;

updating the saved content in the cache;

sending a second response to the user indicating the content has been saved; and

subsequently to sending the second response to the user, sending a sixth request to the primary content management server to save the saved content at the primary content management server.