MSS headend caching strategies

1. A content delivery system for sending requested data to a client based on a client request, comprising:

(a) a broadcasting center comprising a transmission source, wherein the broadcasting center is configured to compile an entire data set; and

(b) a headend within a point of presence (POP), that communicates with the broadcasting center, wherein the headend is configured to:

(1) obtain the entire data set from the broadcasting center;

(2) categorize the entire data set into a plurality of groups;

(3) store, during a first stage of a multiple stage caching strategy consisting of two different caches, the categorized data set in the plurality of groups in an object cache from the two different caches on the headend;

(4) receive the client request from the client;

(5) based on the client request, pick data from one or more of the plurality of groups in the object cache and generate a client response with the picked data;

(6) return the client response to the client and cache, during a second stage of the multiple stage caching strategy, the client response in a response cache from the two different caches on the headend; and

(7) for each future client request received and as part of the multiple stage caching strategy, the headend checks the response cache and returns the cached client response from the response cache if there is a hit, otherwise, the headend generates a new client response from the object cache.

2. The content delivery system of claim 1 , wherein the entire data set is pushed from the broadcasting center to the headend.

3. The content delivery system of claim 1 , wherein the entire data set is retrieved from the broadcasting center via a single request.

4. The content delivery system of claim 1 , wherein the client response comprises an extensible markup language (XML) string.

5. The content delivery system of claim 1 , wherein the client response is keyed by a request uniform resource locator (URL) in the response cache.

6. The content delivery system of claim 1 , wherein the object cache is periodically refreshed based on a type of the data in the data set.

7. The content delivery system of claim 6 , wherein the headend is further configured to clear the response cache when the object cache is refreshed.

8. The content delivery system of claim 1 , wherein the broadcasting center further comprises a data crawler, coupled to the entire data set, that is configured to:

crawl a database to retrieve information;

filter out any unneeded information from the retrieved information leaving remaining information;

store the remaining information in tree-structured files; and

compress the tree-structured files into a compressed file, wherein the entire data set comprises the compressed file.

9. The content delivery system of claim 1 , wherein the client response is a concatenation of a plurality of picked data from the object cache.

10. The content delivery system of claim 1 , wherein:

the data set is categorized into groups based on a customizable period of time;

the client request is for a period of time; and

the client response comprises a concatenation of the groups based on the requested period of time.

11. The content delivery system of claim 1 , wherein the client comprises a mobile client.

12. The content delivery system of claim 1 , wherein the response cache comprises data that is not static.

13. A method for caching data in response to a

client request, comprising:

obtaining an entire data set from a server;

categorizing the entire data set into a plurality of groups;

storing, during a first stage of a multiple stage caching strategy consisting of two different caches, the categorized data set in the plurality of groups in an object cache from the two different caches;

receiving the client request from the client;

based on the client request, picking data from one or more of the plurality of groups in the object cache and generating a client response with the picked data;

returning the client response to the client and caching, during a second stage of the multiple stage caching strategy, the client response in a response cache from the two different caches; and

for each future client request received and as part of the multiple stage caching strategy, checking the response cache and returning the cached client response from the response cache if there is a hit, otherwise, generating a new client response from the object cache.

14. The method of claim 13 , wherein the entire data set is retrieved from the server via a single request.

15. The method of claim 13 , wherein the client response comprises an extensible markup language (XML) string.

16. The method of claim 13 , wherein the client response is keyed by a request uniform resource locator (URL) in the response cache.

17. The method of claim 13 , wherein the object cache is periodically refreshed based on a type of the data in the data set.

18. The method of claim 17 , further comprising clearing the response cache when the object cache is refreshed.

19. The method of claim 13 , further comprising the server:

crawling a database to retrieve information;

filtering out any unneeded information from the retrieved information leaving remaining information;

storing the remaining information in tree-structured files; and

compressing the tree-structured files into a compressed file, wherein the entire data set comprises the compressed file.

20. The method of claim 13 , wherein the client response is a concatenation of a plurality of picked data from the object cache.

21. The method of claim 13 , wherein:

the data set is categorized into groups based on a customizable period of time;

the client request is for a period of time; and

the client response comprises a concatenation of the groups based on the requested period of time.

22. The method of claim 13 , wherein the client comprises a mobile client.

23. The method of claim 13 , wherein the response cache comprises data that is not static.