Method and system for file-system based caching
A method and system for file-system based caching can be used to improve efficiency and security at network sites. In one set of embodiments, the delivery of content and storing content component(s) formed during generation of the content may be performed by different software components. Content that changes at a relatively high frequency or is likely to be regenerated between requests may not have some or all of its corresponding files cached. Additionally, extra white space may be removed before storing to reduce the file size. File mapping may be performed to ensure that a directory within the cache will have an optimal number of files. Security at the network site may be increased by using an internally generated filename that is not used or seen by the client computer. Many variations may be used is achieving any one or more of the advantages described herein.
1. A method for file-system based caching, comprising:
at a cache manager embodied on non-transitory computer memory including instructions executable by a processor:
receiving content and tracking information associated with the content, the content generated by a page generator, the page generator communicatively connected to the cache manager, the cache manager and the page generator operating in an enterprise computing environment, the content including one or more content components and metadata;
based on the metadata, determining whether to cache any specific content component of the one or more content components;
determining that a first content component of the one or more content components is to be cached;
determining a location in a hierarchical file-system based cache managed by the cache manager, the location corresponding to a mapped filename previously determined for the first content component, wherein the mapped filename specifies a name for the first content component and a path within the file-system for the first content component; and
storing the first content component in the file-system based cache at the location corresponding to the mapped filename.
2. The method according to claim 1 , wherein the tracking information is generated by an application programming interface interfacing the cache manager and the page generator.
3. The method according to claim 1 , wherein the tracking information comprises an instruction used by the page generator in generating the first content component.
4. The method according to claim 1 , wherein the cache manager uses the tracking information to store a network page and the first content component in the file-system based cache as two separately cached pages with a reference to the first content component left in the network page.
5. The method according to claim 1 , wherein the first content component is referenced by one or more network pages stored in the file-system based cache and wherein the first content component is stored in the file-system based cache only once.
6. The method according to claim 1 , wherein the metadata comprises information about where to cache the first content component if the first content component is to be cached.
7. A system for file-system based caching, comprising:
at least one processor;
non-transitory computer memory including instructions executable by the at least one processor;
a hierarchical file-system based cache; and
a cache manager embodied on the non-transitory computer memory, the instructions when executed by the at least one processor cause the cache manager to:
receive content and tracking information associated with the content, the content generated by a page generator, the page generator communicatively connected to the cache manager, the cache manager and the page generator operating in an enterprise computing environment, the content including one or more content components and metadata;
based on the metadata, determine whether to cache any specific content component of the one or more content components;
determine that a first content component of the one or more content components is to be cached;
determine a location in the file-system based cache, the location corresponding to a mapped filename previously determined for the first content component, wherein the mapped filename specifies a name for the first content component and a path within the file-system for the first content component; and
store the first content component in the file-system based cache at the location corresponding to the mapped filename.
8. The system of claim 7 , wherein the tracking information is generated by an application programming interface interfacing the cache manager and the page generator.
9. The system of claim 7 , wherein the tracking information comprises an instruction used by the page generator in generating the first content component.
10. The system of claim 7 , wherein the cache manager uses the tracking information to store a network page and the first content component in the file-system based cache as two separately cached pages with a reference to the first content component left in the network page.
11. The system of claim 7 , wherein the first content component is referenced by one or more network pages stored in the file-system based cache and wherein the first content component is stored in the file-system based cache only once.
12. The system of claim 7 , wherein the metadata comprises information about where to cache the first content component if the first content component is to be cached.
13. The system of claim 7 , wherein the file-system based cache is embodied on a volatile memory that is part of or separate from the non-transitory computer memory.
14. A computer program product for file-system based caching, comprising:
at least one non-transitory computer readable medium storing instructions executable by at least one processor to implement a cache manager for managing a hierarchical file-system based cache, the instructions when executed by the at least one processor cause the cache manager to:
receive content and tracking information associated with the content, the content generated by a page generator, the page generator communicatively connected to the cache manager, the cache manager and the page generator operating in an enterprise computing environment, the content including one or more content components and metadata;
based on the metadata, determine whether to cache any specific content component of the one or more content components;
determine that a first content component of the one or more content components is to be cached;
determine a location in the file-system based cache, the location corresponding to a mapped filename previously determined for the first content component, wherein the mapped filename specifies a name for the first content component and a path within the file-system for the first content component; and
store the first content component in the file-system based cache at the location corresponding to the mapped filename.
15. The computer program product of claim 14 , wherein the tracking information is generated by an application programming interface interfacing the cache manager and the page generator.
16. The computer program product of claim 14 , wherein the tracking information comprises an instruction used by the page generator in generating the first content component.
17. The computer program product of claim 14 , wherein the cache manager uses the tracking information to store a network page and the first content component in the file-system based cache as two separately cached pages with a reference to the first content component left in the network page.
18. The computer program product of claim 14 , wherein the first content component is referenced by one or more network pages stored in the file-system based cache and wherein the first content component is stored in the file-system based cache only once.
19. The computer program product of claim 14 , wherein the metadata comprises information about where to cache the first content component if the first content component is to be cached.
20. The computer program product of claim 14 , wherein the file-system based cache is embodied on a volatile memory that is part of or separate from the at least one non-transitory computer readable medium.