CACHING RESOURCES

• US 20120191773A1
• Filed: 01/26/2011
• Published: 07/26/2012
• Est. Priority Date: 01/26/2011
• Status: Abandoned Application

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Appleton, Benjamin C.
• Application Number:
  US13/014,689
• Publication Number:
  US 20120191773A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for caching tiles in an interactive mapping system. A request is received from a first client, the request being for a root node of a directory structure in which resource locators for nodes are generated based on a hash of resource locators of respective descendant nodes, and wherein leaf nodes are associated with corresponding resource locators for tiles in an interactive mapping system. A first configuration of tiles is served to the first client as cacheable resources. A new node is added to the directory structure corresponding to a new version of a tile. A second configuration of tiles is served to a second client, while continuing to serve the first configuration of tiles to clients that requested the root node before the resource locators for ancestor nodes of the new node were added.

Claims

1. A method for caching tiles in an interactive mapping system comprising:

receiving, from a first client, a request for a root node of a directory structure in which resource locators for nodes are generated based on a hash of resource locators of respective one or more descendant nodes, wherein requests for parent nodes generate responses containing resource locators of respective one or more descendant nodes, and wherein leaf nodes are associated with corresponding resource locators for tiles in an interactive mapping system;

serving, to the first client, a first configuration of tiles, wherein each intermediate node and each tile is served as a cacheable resource;

receiving an indication of a new node added to the directory structure, the new node corresponding to a new version of a tile;

adding to the directory structure one or more new ancestor nodes of the new node;

receiving, from a second client, a request for the root node; and

serving, to the second client, a second configuration of tiles including the new node, while continuing to serve the first configuration of tiles to one or more other clients that requested the root node before the one or more new ancestor nodes of the new node were added.

2. The method of claim 1, wherein adding one or more new ancestor nodes of the new node comprises switching from serving the first configuration of tiles to serving the second configuration of tiles after a new root node is added.

3. The method of claim 2, wherein switching to serving the second configuration of tiles comprises swapping a root node indicator from the root node to the new root node.

4. The method of claim 3, further comprising serving, in response to receiving, from a second client, a request for the root node, a response containing resource locators of one or more descendant nodes of the new root node.

5. The method of claim 1, where the resource locators for tiles include a version.

6. The method of claim 1, further comprising serving the second configuration of tiles with an indication that one or more tiles are cacheable.

7. The method of claim 1, where updating resource locators for each of one or more ancestor nodes of the new node comprises adding to the directory structure the one or more ancestor nodes for the new node.

8. The method of claim 1, where the resource locators for tiles include map coordinates.

9. The method of claim 1, where the resource locators for tiles include a hash of tile data.

10. The method of claim 1, where resource locators for the root node and each parent node are generated by a hash function.

11. The method of claim 10, where resource locators for the root node and each parent node are generated by a hash of a concatenation of resource locators of one or more respective descendant nodes.

12. The method of claim 1, further comprising generating a separate directory structure for each of one or more zoom levels in the interactive mapping system.

13. The method of claim 1, where the directory structure is a quadtree or a B-tree.

14. The method of claim 1, where the indication that the tile is cacheable comprises an HTTP header.

15. A system comprising:

one or more computers; and

a computer-readable storage device storing instructions that, when executed by the one or more computers, cause the one or more computers to perform operations comprising;

receiving, from a first client, a request for a root node of a directory structure in which resource locators for nodes are generated based on a hash of resource locators of respective one or more descendant nodes, wherein requests for parent nodes generate responses containing resource locators of respective one or more descendant nodes, and wherein leaf nodes are associated with corresponding resource locators for tiles in an interactive mapping system;

serving, to the first client, a first configuration of tiles, wherein each intermediate node and each tile is served as a cacheable resource;

receiving an indication of a new node added to the directory structure, the new node corresponding to a new version of a tile;

adding to the directory structure one or more new ancestor nodes of the new node;

receiving, from a second client, a request for the root node; and

serving, to the second client, a second configuration of tiles including the new node, while continuing to serve the first configuration of tiles to one or more other clients that requested the root node before the one or more new ancestor nodes of the new node were added.

16. The system of claim 15, wherein adding one or more new ancestor nodes of the new node comprises switching from serving the first configuration of tiles to serving the second configuration of tiles after a new root node is added.

17. The system of claim 16, wherein switching to serving the second configuration of tiles comprises swapping a root node indicator from the root node to the new root node.

18. The system of claim 17, where the operations further comprise serving, in response to receiving, from a second client, a request for the root node, a response containing resource locators of one or more descendant nodes of the new root node.

19. The system of claim 15, where the resource locators for tiles include a version.

20. The system of claim 15, where the operations further comprise serving the second configuration of tiles with an indication that one or more tiles are cacheable.

21. The system of claim 15, where updating resource locators for each of one or more ancestor nodes of the new node comprises adding to the directory structure the one or more ancestor nodes for the new node.

22. The system of claim 15, where the resource locators for tiles include map coordinates.

23. The system of claim 15, where the resource locators for tiles include a hash of tile data.

24. The system of claim 15, where resource locators for the root node and each parent node are generated by a hash function.

25. The system of claim 24, where resource locators for the root node and each parent node are generated by a hash of a concatenation of resource locators of one or more respective descendant nodes.

26. The system of claim 15, where the operations further comprise generating a separate directory structure for each of one or more zoom levels in the interactive mapping system.

27. The system of claim 15, where the directory structure is a quadtree or a B-tree.

28. The system of claim 15, where the indication that the tile is cacheable comprises an HTTP header.