CN116501408A - Method and computer system for managing resource loading process - Google Patents

Abstract

The present application relates to web technology, and more particularly, to a method for managing resource loading procedures and a computer system implementing the method, and a computer readable storage medium having stored thereon a computer program implementing the method. According to one aspect of the present application, a method for managing a resource loading process includes the following steps performed at a web server: in response to a web page access request from a client, determining a set of resources associated with an object contained in the accessed web page; determining the extracted priority order of the resources in the set; extracting resources in the set according to the determined priority order; and returning a response message containing the resources in the set to the client.

Description

Method and computer system for managing resource loading process

Technical Field

The present application relates to web technology, and more particularly, to a method for managing resource loading procedures and a computer system implementing the method, and a computer readable storage medium having stored thereon a computer program implementing the method.

Background

The web page is a basic information unit of a website, is composed of various information such as characters, pictures, animation, sound and the like and links, and is associated with other web pages or websites and jumped through the links. Web pages described in Hypertext (Hypertext) are typically displayed by a program called a Web browser (Web browser). The web browser loads the resources required to render the web page from the web server and utilizes those resources to render the web page at the client.

Modern web applications typically use multiple JavaScript or CSS frameworks. As the number of scripts increases, the number of HTTP requests also increases. This will result in increased page load time and reduced performance, especially when network speed is limited and loading resources are large. In addition, because the site manager cannot perceive the loading state, it is difficult to make a quick response when the browser requests "click", thus giving the user a poor experience, which is particularly the case for large complex Web applications.

Disclosure of Invention

It is an object of the present application to provide a method for managing a resource loading process and a computer system implementing the method that can provide a powerful and flexible resource loading management capability while being compatible with existing website resource loading approaches.

According to one aspect of the present application, a method for managing a resource loading process includes the following steps performed at a web server:

in response to a web page access request from a client, determining a set of resources associated with an object contained in the accessed web page;

determining the extracted priority order of the resources in the set;

extracting resources in the set according to the determined priority order; and

and returning a response message containing the resources in the set to the client.

Optionally, in the above method, the following steps are performed before determining the priority order:

resources that do not match the resource security policy are excluded from the collection.

In addition to one or more of the features described above, in the method described above, the priority order is preset or dynamically adjusted after receiving a web page access request.

Further, in the above method, the priority order in which the various types of resources are extracted is set in advance based on at least one of the following: the importance of the objects associated with the resource in the accessed web page, the network bandwidth occupied by the resource extraction, the preferences of the web page writer, and the user preferences.

Or further, in the above method, the priority order in which the resources in the collection are extracted is dynamically adjusted based on the presentation characteristics of the accessed web pages at the client.

Still further, in the above method, the presentation features include one or more of: the existence of the object associated with the resource in the current web page view and the location of the object associated with the resource in the web page file.

In addition to one or more of the features described above, in the above method, the resources in the collection are extracted in the following manner:

for resources with the same priority order, the extraction operation is started as synchronously as possible;

for the resources with the same priority order, if synchronous starting of the extraction operation cannot be realized, starting the resources sequentially according to the expected loading time length of the resources.

Further, in the above method, for each resource in the set, the extracting operation includes:

determining whether the resource exists in a cache of the web server;

if so, the resource is directly fetched from the cache, otherwise, the resource is fetched by accessing other storage locations and the fetched resource is stored in the cache.

Still further in the foregoing, the extracting operation further includes, for each resource in the set:

if the resource is not successfully extracted within the set time period, the extraction operation is terminated.

In accordance with another aspect of the present application, a resource loading process is managed with a computer system comprising:

one or more processors;

a memory having stored thereon a computer program that runs on the processor to perform the following operations:

in response to a web page access request from a client, determining a set of resources associated with an object contained in the accessed web page;

determining the extracted priority order of the resources in the set;

extracting resources in the set according to the determined priority order; and

and returning a response message containing the resources in the set to the client.

Optionally, in the above computer system, the following operations are performed before determining the priority order:

resources that do not match the resource security policy are excluded from the collection.

In addition to one or more of the features described above, in the computer system described above, the priority order is preset or dynamically adjusted after receiving a web page access request.

Further, in the above computer system, the priority order in which the various types of resources are extracted is set in advance based on at least one of: the importance of the objects associated with the resource in the accessed web page, the network bandwidth occupied by the resource extraction, the preferences of the web page writer, and the user preferences.

Or further, in the above computer system, the priority order in which the resources in the collection are extracted is dynamically adjusted based on the presentation characteristics of the accessed web pages at the client.

Still further, in the above computer system, the presentation features include one or more of: the existence of the object associated with the resource in the current web page view and the location of the object associated with the resource in the web page file.

In addition to one or more of the features described above, in the computer system described above, the resources in the collection are extracted in the following manner:

for resources with the same priority order, the extraction operation is started as synchronously as possible;

for the resources with the same priority order, if synchronous starting of the extraction operation cannot be realized, starting the resources sequentially according to the expected loading time length of the resources.

Further, in the above computer system, the extracting operation includes, for each resource in the set:

determining whether the resource exists in a cache of the web server;

if so, the resource is directly fetched from the cache, otherwise, the resource is fetched by accessing other storage locations and the fetched resource is stored in the cache.

Still further, in the above computer system, the extracting operation further includes, for each resource in the set:

if the resource is not successfully extracted within the set time period, the extraction operation is terminated.

According to another aspect of the present application, there is provided a computer readable storage medium having instructions stored therein, characterized in that the method as described above is implemented by execution of the instructions by a processor.

In some embodiments of the present application, the method for managing the resource loading process may be implemented by modifying the control logic of an application (e.g., resource loading manager) that was originally running on a web server, thus eliminating the need to re-develop a new application and also not significantly increasing the occupation of network bandwidth. In addition, in some embodiments, on the premise of being fully compatible with the resource loading process based on the W3C standard, by means such as presetting a priority order and dynamically adjusting the order when processing web page access requests, and setting or adjusting the priority order based on various rules, a powerful and flexible resource loading management capability is provided, so that developers can easily cope with the complexity of large website applications in the development process. Furthermore, in some embodiments, by using a cache to store the loaded resources, the reusability of resource loading can be improved, and the loading speed can be increased, thereby improving the website performance and user experience.

Drawings

The foregoing and/or other aspects and advantages of the present application will become more apparent and more readily appreciated from the following description of the various aspects taken in conjunction with the accompanying drawings in which like or similar elements are designated with the same reference numerals.

FIG. 1 is a flow chart of a method for managing a resource loading process according to some embodiments of the present application.

FIG. 2 is a flow chart of a method for prioritizing resource loads according to further embodiments of the present application.

Fig. 3 is a schematic diagram of execution timing of an extraction operation according to further embodiments of the present application.

Fig. 4 is a flow chart of an extraction operation execution process according to further embodiments of the present application.

Fig. 5 is a schematic block diagram of a typical computer system.

Detailed Description

The present application is described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments of the application are shown. This application may, however, be embodied in different forms and should not be construed as limited to the embodiments set forth herein. The above-described embodiments are provided to fully complete the disclosure herein so as to more fully convey the scope of the application to those skilled in the art.

In this specification, terms such as "comprising" and "including" mean that there are other elements and steps not directly or explicitly recited in the description and claims, nor do the subject matter of the present application exclude the presence of other elements and steps.

Unless specifically stated otherwise, terms such as "first" and "second" do not denote a sequential order of elements in terms of time, space, size, etc., but rather are merely used to distinguish one element from another.

FIG. 1 is a flow chart of a method for managing a resource loading process according to some embodiments of the present application. Illustratively, the steps of the method shown in FIG. 1 are performed at a web server or web site.

Specifically, the method shown in fig. 1 includes the steps of:

step 101: receipt of web page access requests

In step 101, a web server receives a web page access request from a client. Illustratively, a web browser of the client parses a URL input by a user, generates a web access request in HTTP format, and then sends the web access request out through a network protocol through an operating system of the client. The request may pass through various routers and switches and eventually reach the web server.

Step 102: determination of resources

A web page is primarily composed of structural, performance, and behavioral components, each of which may contain multiple elements or objects. Examples of such elements or objects include, but are not limited to: files, cascading style sheets, pictures, fonts, scripts, multimedia, links, etc. In some embodiments, the web page may be written in the following standardized language: structured standard languages (including, for example, extensible markup language (XML) and extensible hypertext markup language (XHTML)), presentation standard languages (including, for example, cascading Style Sheets (CSS)), behavior standards (including, for example, object models and scripting languages), and the like.

In order to be able to render the accessed web page on the web browser, the web server needs to include resources associated with the objects in the web page in the response message returned to the client. Table 1 is an exemplary list of various types of resources.

TABLE 1

In step 102, in response to the received web page access request, the web page server will determine various resources (e.g., one or more of the resource types listed in Table 1) associated with the object in the accessed web page. Illustratively, the set of resources associated with an object in the accessed web page is denoted as { r } _i -where r _i Representing the i-th resource in the set of resources.

Step 103: limiting resource loading

In step 103, the web server performs a checking operation based on the resource security policy to improve the security of the web page. Specifically, the web server will set the resources { r } _i Resource culling or exclusion in the process that does not match the resource security policy. For example, assume the resource set { r } _i A file or script resource written in a javascript script language (e.g. marked as "untitled. Js") is included in the file, and the script code with suspicious or security risk is included in the file, the script resource "untitled. Js" will not be loaded based on the set resource security policy. Illustratively, the set of resources associated with the object in the accessed web page after the above-described inspection operation is denoted as { r' _j }, where r' _j Representing the j-th resource in the set of resources.

It should be noted that step 103 is optional. After step 102 is performed, the flow shown in fig. 1 may also proceed directly to step 104, which will be described below.

Step 104: determination of priority order of resource loads

In step 104, the web server determines a set of resources { r } _i Either (when no checking based on resource security policies is performed) or a set of resources { r' _j Priority order in which resources in (when performing a check based on resource security policies) are loaded.

In some embodiments, the priority order corresponding to the various types of resources is preset. Illustratively, the priority order of resource loading may include the following levels from high to low: high priority, medium priority, low priority, and idle. When the loading order of a resource is designated as idle, the resource is loaded only when the processor processing power is idle or the network transmission load is small.

Alternatively, the priority order may be preset based on various factors including, but not limited to, the importance of the object associated with the resource in the accessed web page, the network bandwidth occupied by the loading of the resource, and user preferences, for example. In one example, high priority in priority order may be allocated to HTML, CSS, and font type resources, medium priority to preload resources (e.g., resources preloaded by < link rel= "preload" > tag) and script resources, low priority to picture, voice, and video type resources, and idle to prefatch pre-read resources.

In other embodiments, the priority order corresponding to the various types of resources may also be dynamically adjusted by the web server after receiving the web access request. Alternatively, the priority order of the resources in the resource set may be dynamically adjusted based on the presentation characteristics of the accessed web page at the client. In particular, the presentation features include one or more of the following: the existence of the object associated with the resource in the current web page view and the location of the object associated with the resource in the web page file.

FIG. 2 is a flow chart of a method for prioritizing resource loads according to further embodiments of the present application. The flow shown in fig. 2 may be used to implement step 104 in fig. 1.

The method shown in fig. 2 comprises the following steps:

step 201: the web server first retrieves the pre-configured information of the priority order (which information is stored, for example, in the memory or static memory of the web server).

Step 202: the web server is based on pre-configured information for the resource set { r } _i Or resource set { r' _j Resources in the sequence are allocated corresponding priority orders.

Step 203: the web server will adjust the resource set { r } based on the preset trigger conditions _i Or resource set { r' _j Priority order of one or more resources in the list. For example, for a picture resource, the priority order of loading may be adjusted based on whether its associated picture appears within the visual view, i.e., if the associated picture does not appear within the visual view, the picture resource still maintains a default priority order (e.g., low priority), otherwise the priority order is up-scaled to medium or high priority. As another example, a script resource may dynamically adjust the priority order based on the location and attribute tags in which its associated script is located. For example, for a script with a defer/async attribute tag, assuming that the corresponding resource loading order is preset to be low priority, after receiving a web page access request, the priority order of loading the corresponding script resource may be redetermined according to whether the position of the script in the document appears before or after the first picture displayed by the web browser, i.e., if the script appears before the first picture, the priority order of loading is adjusted to be medium priority, otherwise, the priority order remains unchanged.

Step 105: extraction of resources

In step 105, resource sets { r } are sequentially extracted or loaded according to the priority order determined in step 104 _i Or resource set { r' _j Resources in }.

In some embodiments, for the resource set { r } _i Or resource set { r' _j Resources having the same priority order in the sequence, the extraction operations are started as synchronously as possible, and if synchronous starting of the extraction operations cannot be realized, the extraction operations can be started in a random manner or can be started in other manners (for example, the extraction operations are started in sequence according to the expected loading time length of the resources, the user preference or the preference of a webpage writer, etc.).

FIG. 3 is a schematic diagram of execution timing of an extraction operation according to further embodiments of the present application, wherein the horizontal axis represents time, and the gray rectangular bar represents actual loading durations of various resources (time that resource loading actually takes), and the numbers in the rectangular bar represent predicted loading durations of various resources (time that resource loading is predicted to take). In the example shown in fig. 3, it is assumed that the loading order of the resources identified with icon2.Png, s2.Css, 2.Js has a high priority, the loading order of the resources identified with s1.Css, 3.Js has a medium priority, and the loading order of the resources identified with icon1.Js, 4.Js has a low priority. Referring to fig. 3, at the beginning of resource extraction, the extraction operations of resources icon2.Png, s2.Css, 2.Js with high priority are synchronously started; because the time-consuming extraction operations of the high-priority resources are different, the extraction operations of the medium-priority resources s1.Css and 3.Js cannot be synchronously started, and at this time, the extraction operations can be started sequentially based on a set rule, for example, in the example shown in fig. 3, the extraction operation is performed by the resource s1.Css with a shorter expected loading duration before the resource s 3. Js; similarly, because the fetch operations of the medium-priority resources are time-consuming differently and the start-up time points are not consistent, the low-priority resources icon1.Js, 4.Js cannot start fetch operations at the same time, and in the example shown in fig. 3, they are also sequentially executed with the expected load time period.

Fig. 4 is a flow chart of an extraction operation execution process according to further embodiments of the present application. The flow shown in FIG. 4 may be used to implement { r for a set of resources _i Or resource set { r' _j Extraction operation for each resource in the list.

The flow shown in fig. 4 includes the following steps performed by the web server:

step 401: for resource r _i Or r' _j It is determined whether it is present in the cache of the web server. If so, go to step 402, otherwise, go to step 403.

Step 402: extracting resource r directly from cache _i Or r' _j . After completion of step 402, the flow shown in fig. 4 will go to step 106 to be described below.

Step 403: accessing other storage locations (e.g., nonvolatile memory of a web server or other network node) to extract resource r _i Or r' _j 。

Step 404: determiningDetermining whether to successfully extract resource r from other storage locations _i Or r' _j . If the extraction is successful, go to step 405, otherwise, go to step 406.

Step 405: resources r to be extracted from other storage locations _i Or r' _j And storing into a cache. After completion of step 405, the flow shown in fig. 4 will go to step 106.

Step 406: determining whether the execution of step 403 has timed out (i.e., determining whether a set period of time has been exceeded since the beginning of execution of step 403), if so, terminating resource r _i Or r' _j And goes to step 106, otherwise, continues waiting.

Step 106: return of response message

In step 106, the web server returns a response message (e.g., HTTP response message) containing the resources extracted in step 105 to the client. Accordingly, at the client, the web browser parses the response message and presents the requested web page. It should be noted that the response message returned to the client may contain the resource set { r } _i Or resource set { r' _j All resources in } may also contain only a portion of the resources because the fetch operation failed.

FIG. 5 is a schematic block diagram of a typical computer system that may be used to implement the web server described above. As shown in FIG. 5, computer system 50 includes memory 510 (e.g., non-volatile memory such as flash memory, ROM, hard disk drive, magnetic disk, optical disk, and volatile memory such as dynamic random access memory and static random access memory), processor 520, and computer program 530.

The memory 510 stores a computer program 530 executable by the processor 520. In addition, memory 510 may also act as a cache to hold resources extracted from other storage locations (e.g., nonvolatile memory of a web server or other network nodes). The processor 520 is configured to run a computer program 530 stored on the memory 510. One or more of the steps involved in the methods described above with respect to fig. 1-4 may be implemented by running the computer program 530.

According to another aspect of the present application, there is also provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs one or more of the steps comprised in the method described above with reference to fig. 1-4.

Those of skill would appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both.

To demonstrate interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Implementation of such functionality in hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

Although only a few specific embodiments of this application have been described, those skilled in the art will appreciate that this application may be embodied in many other forms without departing from the spirit or scope thereof. Accordingly, the illustrated examples and embodiments are to be considered as illustrative and not restrictive, and the application is intended to cover various modifications and substitutions without departing from the spirit and scope of the application as defined by the appended claims.

The embodiments and examples set forth herein are presented to best explain the embodiments in accordance with the present technology and its particular application and to thereby enable those skilled in the art to make and use the application. However, those skilled in the art will recognize that the foregoing description and examples have been presented for the purpose of illustration and example only. The description as set forth is not intended to cover various aspects of the application or to limit the application to the precise form disclosed.

Claims (10)

1. A method for managing a resource loading process, comprising the steps performed at a web server of:

in response to a web page access request from a client, determining a set of resources associated with an object contained in the accessed web page;

determining the extracted priority order of the resources in the set;

extracting resources in the set according to the determined priority order; and

and returning a response message containing the resources in the set to the client.

2. The method of claim 1, wherein the following steps are performed prior to determining the priority order:

resources that do not match the resource security policy are excluded from the collection.

3. The method of claim 1 or 2, wherein the priority order is preset or dynamically adjusted after receiving a web page access request.

4. A method according to claim 3, wherein the order of priority in which the various types of resources are extracted is preset based on at least one of: the importance of the objects associated with the resource in the accessed web page, the network bandwidth occupied by the resource extraction, the preferences of the web page writer, and the user preferences.

5. The method of claim 3, wherein the priority order in which resources in a collection are extracted is dynamically adjusted based on presentation characteristics of the accessed web pages at the client.

6. The method of claim 5, wherein the presentation features comprise one or more of the following: the existence of the object associated with the resource in the current web page view and the location of the object associated with the resource in the web page file.

7. The method of claim 1 or 2, wherein the resources in the set are extracted in the following way:

for resources with the same priority order, the extraction operation is started as synchronously as possible;

for the resources with the same priority order, if synchronous starting of the extraction operation cannot be realized, starting the resources sequentially according to the expected loading time length of the resources.

8. The method of claim 7, wherein, for each resource in the set, the extracting operation comprises:

determining whether the resource exists in a cache of the web server;

if so, the resource is directly fetched from the cache, otherwise, the resource is fetched by accessing other storage locations and the fetched resource is stored in the cache.

9. A computer system, comprising:

one or more processors;

a memory having stored thereon a computer program that runs on the processor to perform the following operations:

in response to a web page access request from a client, determining a set of resources associated with an object contained in the accessed web page;

determining the extracted priority order of the resources in the set;

extracting resources in the set according to the determined priority order; and

and returning a response message containing the resources in the set to the client.

10. A computer readable storage medium having instructions stored therein, wherein the method of any one of claims 1-8 is implemented by execution of the instructions by a processor.