SYSTEMS AND METHODS FOR CACHING OF MANAGED CONTENT IN A DISTRIBUTED ENVIRONMENT USING A MULTI-TIERED ARCHITECTURE
1 Assignment
0 Petitions
Accused Products
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.
6 Citations
41 Claims
-
1-20. -20. (canceled)
-
21. A system for remote caching, comprising:
-
a remote cache system for use with a primary content management system that manages content, including; a processor; a data store comprising a cache and storing metadata corresponding to content stored in the cache, wherein the content in cache comprises content managed by the primary content management system; and a non-transitory computer readable medium, comprising instruction for; receiving a first request to access content; accessing the data store to determine if first metadata associated with the requested content is stored in the data store; sending a first request to a primary server associated with the primary content management system based on the determination if first metadata associated with the requested content is stored in the data store; receiving a first response from the primary server 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 the 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 second request for the current version of the content to the primary server; receiving the current version of the content; storing the current version of the content in the cache; and providing the current version of the content in response to the first request; receiving the first request associated with the content; sending a third request to the server for the second metadata associated with the content; returning the first response, including the second metadata; receiving the second request for the current version of the content; obtaining the current version of the content from the primary content management system; and returning the current version of the content. - View Dependent Claims (22, 23, 24, 25, 26, 27)
-
-
28. A method for remote caching, comprising:
-
receiving a first request to access content at a remote cache system for use with a primary content management system that manages content, the remote cache system including a data store comprising a cache and storing metadata corresponding to content stored in the cache, wherein the content in cache comprises content managed by the primary content management system; accessing the data store to determine if first metadata associated with the requested content is stored in the data store; sending a first request to a primary server associated with the primary content management system based on the determination if first metadata associated with the requested content is stored in the data store; receiving a first response from the primary server 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 the 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 second request for the current version of the content to the primary server; receiving the current version of the content; storing the current version of the content in the cache; and providing the current version of the content in response to the first request; receiving the first request associated with the content; sending a third request to the server for the second metadata associated with the content; returning the first response, including the second metadata; receiving the second request for the current version of the content; obtaining the current version of the content from the primary content management system; and returning the current version of the content. - View Dependent Claims (29, 30, 31, 32, 33, 34)
-
-
35. A non-transitory computer readable medium, comprising instructions for:
-
receiving a first request to access content at a remote cache system for use with a primary content management system that manages content, the remote cache system including a data store comprising a cache and storing metadata corresponding to content stored in the cache, wherein the content in cache comprises content managed by the primary content management system; accessing the data store to determine if first metadata associated with the requested content is stored in the data store; sending a first request to a primary server associated with the primary content management system based on the determination if first metadata associated with the requested content is stored in the data store; receiving a first response from the primary server 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 the 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 second request for the current version of the content to the primary server; receiving the current version of the content; storing the current version of the content in the cache; and providing the current version of the content in response to the first request; receiving the first request associated with the content; sending a third request to the server for the second metadata associated with the content; returning the first response, including the second metadata; receiving the second request for the current version of the content; obtaining the current version of the content from the primary content management system; and returning the current version of the content. - View Dependent Claims (36, 37, 38, 39, 40, 41)
-
Specification