Selective prefetch scanning
US-8984048-B1 · Mar 17, 2015 · US
US9756108B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9756108-B2 |
| Application number | US-201313868920-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 23, 2013 |
| Priority date | May 29, 2012 |
| Publication date | Sep 5, 2017 |
| Grant date | Sep 5, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A computer-implemented method for preloading resources of a web page is provided. The method includes receiving a user request to navigate to a web page and issuing a request for a root page corresponding to the requested web page, wherein the root page identifies actual resources requested for loading the requested web page. The method also includes determining, based on a prior history of loading the requested web page, anticipated resources that are likely to be requested when loading the requested web page, and requesting the anticipated resources from a server associated with the anticipated resources at least until a time that the root page corresponding to the requested web page is received to determine the actual resources requested for loading the requested web page. Systems and machine-readable media are also provided.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method for preloading resources of a web page, the method comprising: receiving, by a web browser, a user request to navigate to a web page; issuing, by the web browser, a request for a root page corresponding to the requested web page, wherein the root page identifies actual resources required for loading the requested web page; determining, essentially concurrently with the issued root page request and based on a history of prior loading sessions for the same requested web page, anticipated resources that are likely to be requested as part of loading the requested web page; requesting, by the web browser, the anticipated resources from a server; concurrently receiving the requested root page and the requested anticipated resources; and ceasing to receive the requested anticipated resources when a predetermined amount of data for the requested root page has been received. 2. The method of claim 1 , further comprising: determining actual resources requested for loading the web page by parsing the received requested root page; and comparing the anticipated resources to the actual resources, wherein, if one of the determined actual resources corresponds to one of the received anticipated resources, using the received anticipated resource when loading the requested web page. 3. The method of claim 1 , wherein the anticipated resources are received until a time that the entire requested root page corresponding to the requested web page is received and parsed to determine the actual resources requested for loading the requested web page. 4. The method of claim 1 , wherein the prior history of loading the requested web page comprises information on an order in which the actual resources were requested in a previous loading of the requested web page, wherein the requested anticipated resources are requested in the order in which the actual resources were requested in the previous loading. 5. The method of claim 1 , wherein the prior history of loading the requested web page comprises at least one of a number of times that an anticipated resource has corresponded to an actual resource requested for loading the requested web page for a threshold number of consecutive web page loads, a number of times that the anticipated resource has not corresponded to an actual resource requested for loading the requested web page, or a number of times the anticipated resource has not corresponded to an actual resource requested for loading the requested web page consecutively. 6. The method of claim 1 , wherein the prior history of loading the requested web page comprises a cache header for the anticipated resource. 7. The method of claim 1 , wherein the anticipated resources are requested if the anticipated resources are at least one of marked as cacheable or do not have a cache header. 8. The method of claim 1 , wherein the predetermined amount of data is 256 bytes. 9. The method of claim 1 , wherein the step of determining the anticipated resources comprises determining that the prior history of loading the web page is available for more than a predetermined number of previous loads of the web page. 10. The method of claim 1 , wherein the step of determining the anticipated resources further comprises determining the anticipated resources based on a resource cache, wherein the resource cache comprises a plurality of cached resources that have been previously requested for loading the requested web page. 11. The method of claim 10 , further comprising updating the plurality of cached resources before receiving the user request to navigate to the web page. 12. A system for preloading resources of a web page, the system comprising: a memory storing executable instructions; and a processor coupled to the memory configured to execute the stored executable instructions to: receive, by a web browser, a user request to navigate to a web page; issue, by the web browser, a request for a root page corresponding to the requested web page, wherein the root page identifies actual resources required for loading the requested web page; determine, essentially concurrently with the issued root page request and based on a history of prior loading sessions for the same requested web page, anticipated resources that are likely to be requested as part of loading the requested web page; request, by the web browser, the anticipated resources from a server; concurrently receive the requested root page and the requested anticipated resources; cease to receive the requested anticipated resources when a predetermined amount of data for the requested root page has been received; determine actual resources requested for loading the web page by parsing the received requested root page; and compare the anticipated resources to the actual resources, wherein if one of the determined actual resources corresponds to one of the received anticipated resources, use the received anticipated resource when loading the web page. 13. The system of claim 12 , wherein the anticipated resources are received until a time that the entire requested root page corresponding to the requested web page is received and parsed to determine the actual resources requested for loading the requested web page. 14. The system of claim 12 , wherein the prior history of loading the requested web page comprises information on an order in which the actual resources were requested in a previous loading of the requested web page. 15. The system of claim 12 , wherein the prior history of loading the requested web page comprises at least one of a number of times an anticipated resource has corresponded to an actual resource associated with loading the requested web page, a number of times the anticipated resource has not corresponded to an actual resource associated with loading the requested web page, or a number of times the anticipated resource has not corresponded to an actual resource requested for loading the requested web page consecutively. 16. The system of claim 12 , wherein the prior history of loading the requested web page comprises a cache header for the anticipated resource. 17. The system of claim 12 , wherein the anticipated resources are requested if the anticipated resources are at least one of marked as cacheable or do not have a cache header. 18. The system of claim 12 , wherein the step of determining the anticipated resources further comprises determining the anticipated resources based on a resource cache, wherein the resource cache comprises a plurality of cached resources that have been previously requested for loading the requested web page. 19. A non-transitory machine-readable storage medium comprising machine-readable instructions for causing a processor to execute a method for preloading resources of a web page, the method comprising: receiving, by a web browser, a user request to navigate to a web page; issuing, by the web browser, a request for a root page corresponding to the requested web page, wherein the root page identifies actual resources required for loading the requested web page; determining, essentially concurrently with issuing the root page request and based on a history of prior loading sessions for the same requested web page, anticipated resources that are likely to be requested as part of loading the requested web page; determining whether the anticipated resources are at least marked as cacheable or do not have a cache header; requesting the anticipated resources from a server when the predicted resources are de
Electricity · mapped topic
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
Physics · mapped topic
Pre-fetching or pre-delivering data based on network characteristics · CPC title
of access to content, e.g. by caching · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.