Method and system for dynamic distributed data caching
First Claim
Patent Images
1. A client system in a cache community for community data caching, comprising:
- a storage space including a dedicated cache portion operable to cache content in the cache community;
a cache module operable to manage content cached in the cache portion of the storage space, the cache module including a location table operable to identify locations of caches within the cached community where content should be cached;
a processor operable to generate a request for content, the cache module operable to intercept and process the request, determine where the content should be located, query a remote cache module where the content should be located, and deliver requested content from any cache in the cache community when cached or from an origin server when not cached;
wherein the cache module is configurable to limit consumption of resources in the client system.
5 Assignments
0 Petitions
Accused Products
Abstract
A method and system for dynamic distributed data caching is presented. The system includes one or more peer members and a master member. The master member and the one or more peer members form cache community for data storage. The master member is operable to select one of the one or more peer members to become a new master member. The master member is operable to update a peer list for the cache community by removing itself from the peer list. The master member is operable to send a nominate master message and an updated peer list to a peer member selected by the master member to become the new master member.
146 Citations
20 Claims
-
1. A client system in a cache community for community data caching, comprising:
-
a storage space including a dedicated cache portion operable to cache content in the cache community; a cache module operable to manage content cached in the cache portion of the storage space, the cache module including a location table operable to identify locations of caches within the cached community where content should be cached; a processor operable to generate a request for content, the cache module operable to intercept and process the request, determine where the content should be located, query a remote cache module where the content should be located, and deliver requested content from any cache in the cache community when cached or from an origin server when not cached; wherein the cache module is configurable to limit consumption of resources in the client system. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A method for community data caching, comprising:
-
allocating a dedicated cache portion in a storage space of a distributed location as part of a cache community for caching content; managing content cached in the cache portion of the storage space; populating a location table at the distributed location, the location table identifying each distributed location of cache portions within the cached community where particular content is desired to be cached; intercepting a request for content; determining where the content should be located; sending a query to a particular distributed location where the content should be located; delivering the requested content from the particular distributed location when cached therein; retrieving the content from an origin server when the requested content is not cached at the particular distributed location; dynamically limiting consumption of resources in the distributed location for data caching. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. A non-transitory computer readable medium including code for community data caching, the code operable to:
-
allocate a dedicated cache portion in a storage space of a distributed location as part of a cache community for caching content; manage content cached in the cache portion of the storage space; populate a location table at the distributed location, the location table identifying each distributed location of cache portions within the cached community where particular content is desired to be cached; intercept a request for content; determine where the content should be located; send a query to a particular distributed location where the content should be located; deliver the requested content from the particular distributed location when cached therein; retrieve the content from an origin server when the requested content is not cached at the particular distributed location; dynamically limit consumption of resources in the distributed location for data caching. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification