JP5465821B2 - Distribution dynamic web page caching system - Google Patents

Description

  The present invention relates to distributed dynamic web page caching.

Problems to be solved by the prior art and the invention

  Computer networks, such as the Internet and private company networks, allow users to retrieve information from a wide variety of information sources. They also allow publishers, information providers, advertisers and other information sources to provide information to these users. A “server” is a computer system that is connected to a network and stores and supplies information. One type of server on the Internet is a web server that provides a connection to a website. Each website has a tree structure for storing information such as text, images, sounds, animations, and 3D simulations, and makes one or more “web pages” formatted available. In addition to many publishers such as newspapers and magazines, companies, individuals and organizations have also established web pages. A “client” is a computer system that is connected to a network and generally controlled by users who may request information from servers on the network. In particular, clients at various locations can view a web page by “downloading” a copy of the web page from the server where the web page is stored.

Means for Solving the Invention

  In one aspect, the invention features a method of dynamic web page caching that includes receiving and confirming a web page request from a client to determine whether the page template and page component tag of the web page are in local cache memory. Yes. If the page template and page component tag are not in the local cache memory, the page template and page component tag are downloaded from the server to the local cache memory. The web page is assembled from the page template and page component tags in the local cache memory, and the web page is sent to the client.

Embodiments may include one or more of the following.
Passing a cookie representing the client session identifier (ID) from the server to the local cache memory because of the possibility of managing the session.
The page component tag may include page position information, parameters for passing from the server to the page template, and time limit information. They may also include binary large object (blob) components.

  In another embodiment, the invention features a network including a server having a collection of data including web pages, and a server link connecting the server to the Internet. The cache system link connects the dynamic web caching system to the Internet. The dynamic web caching system includes an assembly engine for assembling a web page from components detected in a local cache, and a distribution engine for delivering the web page to a client.

Embodiments of the present invention have one or more of the following advantages.
Assembling a web page containing dynamic components minimizes or eliminates the request to the client, the request to assemble the page requested by the server, and the web page to the client over the Internet. Make sending more closely.

  The details of the specification of the dynamic page component are cached at the end of the network that facilitates the assembly and distribution of the dynamic component away from the server.

  Caching the assembly and distribution of dynamic page components at the end of the network increases the vast number of dynamic page views each day. This is because a vast number of dynamic page components are generated without going through the Internet.

  If the satellite server and / or server is down, i.e. offline, other satellite servers can perform request processing to assemble and distribute pages. Synchronization between satellite servers is not required. Each satellite server is independent and independent of any other hygiene server bundle.

  One or more details of the invention will be described in conjunction with the following drawings and description. Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.

  As shown in FIG. 1, the web page 10 defines one or more areas such as areas 14, 16, 18, and 20. Each region 14, 16, 18, 20 is also referred to as a component and is part of the web page template 12. Components 14-20 may include different types of information such as text, images, graphics, animations, timers, links, and the like. Each component 14-20 of the web page template 12 may be further layered as static or dynamic. Static components do not change for a period of time. A dynamic component is a component that is the result of computer processing that is performed when a web page 10 is requested. Due to their characteristics, dynamic components exist at discrete times and are typically assembled when a client requests them from a server. A server that uses the specification characteristics of a dynamic component establishes a web page and delivers the web page to the requesting client.

  An example of a dynamic component is one that includes the current weather. The current weather can change during the request, so that a response can be assembled to the user's request. Other examples of dynamic components include personal messages such as “Hi Joe”.

  The web page 10 is generally on a server (not shown). The client requests viewing of the web page 10 from the server. A server with details of each component 14-20 in the web page 10 assembles the web page 10 with the associated component 14-20 and sends the web page 10 to the requesting client. In practice, each component 14-20 is a static component, and the web page 10 is pre-assembled and stored in a database associated with the server. Therefore, when the web page 10 is requested by the client, the server loads the previously stored web page and delivers it to the browser of the client system. If one or more components 14-20 are dynamic, the server assembles the dynamic components with component details only known to the server prior to delivering web page 10 to the client.

  A server capable of responding to the web page 10 can recognize the components 14 to 20 of the web page template 12 in detail. Each component 14-20 is defined by a set of parameters or tags that are known only to the server system. For example, each component includes an associated web page template 12, a tag that is required to obtain information contained in the component, and period information, no matter what parameters need to pass through the component. Have. These tags may include page information and blob information. A blob is a binary large object and is used to represent an image, for example. Only the server recognizes each parameter. The components are surrounded by each component 14-20 that allows the server to assemble and serve the web page 10 to the requesting client.

  As shown in FIG. 2, a network 40 having a distributed dynamic web page caching process includes a number of Internet service providers (ISPs) 42, 44, 46, 48 connected to the Internet 50. ISPs 42-48 provide client and server computer systems that connect to the Internet 50. Network 40 includes a server 52 connected to ISP 44. Network 40 also shows client 54 having browser 56 connected to ISP 48. The network 40 includes an arrangement of a satellite server connected to the ISP 48 and a satellite server 60 connected to the Internet 50. In the preferred embodiment, the network 40 includes either a satellite server 58 connected to the ISP 48 or a satellite server 60 connected to the Internet 50. In other embodiments, the satellite servers may be located at other locations that are “terminal” to the network 40. Generally, the network has one satellite server per port and per domain. When the client 54 requests “provide” a web page from the server 52 via the browser 56, for example, in cooperation with the server 52, the satellite server 58 assembles the static and dynamic components of the web page and Give page.

  As shown in FIG. 3, the satellite server 80 includes a content server 82 and a content server 84. Content servers 82 and 84 are linked to web server 86 and web server 88 through separate plug-ins 90 and 92. The web servers 86, 88 are linked to cache memories displayed separately as 94, 96, 98, 100. Each cache memory 94-100 is linked to the local director 102. Local director 102 includes a link 104 that provides communication to the ISP or the Internet.

  In processing, when a request to provide a web page is received at link 104, the local director 102 checks the cache memory 94-100 to see if the requested web page template and component tag are present. Explore through. If the requested web page component tag is included in one of the cache memories 94-100, the content server 82 or content server 84 assembles and requests the web page from the cached template and component tag. The assembled web page is sent to the client over link 104.

  As shown in FIG. 4, the distributed dynamic web page caching procedure 120 includes receiving 122 a page request from a client. The procedure 120 checks at step 124 whether the requested page component tag and web page template are in one of the satellite server caches. If the web page and the associated web page template and page component tag are in the satellite system server cache, the satellite system assembles and requests the web page at step 126 with the web page template and page component tag. The assembled page is delivered to the client at step 128. If the web page template and component tag for the requested web page are not in the satellite server cache, the procedure 120 obtains the web page template and associated page component tag from the server at step 130. If the information necessary to assemble the page component is obtained from the server, the server accumulates information from one of those cache memories at step 132. The procedure 120 sends a web page assembled according to the web page template and a page component tag associated with the satellite server in step 134, and stores the web page template and component tag in the satellite server cache memory in step 136. At step 128, the assembled page is delivered to the requesting client.

  Using procedure 120, the second page access will find the requested information needed to assemble the requested web page in the satellite server cache memory. This is because the satellite server has knowledge acquired from the server, that is, knowledge to create a web page from the presence of the web page template and the page component tag associated in the satellite server cache memory. The satellite server need not have the logic to create a dynamic page component, but the satellite server can obtain the necessary logic from the server.

  Typically, procedure 120 maintains a replicated cache. That is, all cache components are on every content server in the network. Therefore, if one satellite server fails, the other hygiene server will perform the work necessary to provide the requested web page. Synchronization between satellite servers is not required. Each satellite server is independent and independent of any other hygiene server bundle.

  Procedure 120 also maintains session information. In an embodiment of the invention, the session information is contained in a cookie that passes between the client and the satellite server. In this method, a new session is not created by a second request for a web page by the same user requesting a web page from the hygiene server.

  While numerous embodiments of the present invention have been described, various modifications will be understood without departing from the scope or essence of the invention. Therefore, other embodiments are within the scope of the following claims.

  It is a block diagram of a web page.   1 is a block diagram of a network including a satellite server.   FIG. 3 is a block diagram of the satellite server of FIG. 2.   FIG. 3 is a diagram showing a flow of a distributed dynamic web page caching procedure on the computer network of FIG. 2.

12 Web page template 14, 16, 18, 20 Component 42, 44, 46, 48 ISP
50 Internet 52 Server 54 Client 56 Browser 58, 60 Satellite server 82, 84 Content server 94, 96, 98, 100 Cache 86, 88 Web server 90, 92 Plug-in

Claims (3)

A computer-implemented method for generating a dynamic web page, comprising:
From the client through the network comprises the step of receiving a request for Oite web page on a computer, the web page is associated with a web page template defining one or more components of the web page, each component, Refer to different areas of the web page ,
The method
Said web page web page template and page component tag of comprising a step of confirming whether a local cache memory in the computer, each page component defined by the web page template, one or more of the page The page component tag associated with a component tag identifies where to get the information in the component, the deadline information for the component, and binary large object (blob) information, where the parameter Is passed from the server to the component, the parameter is known only to the server ,
In response to the confirmation, if the web page template and page component tag is not in the local cache memory, the method comprising over the network to download a web page template and page component tag of the web page in the local cache memory from the server,
Assembling a web page from a web page template and a page component tag in the local cache memory;
Providing the client with the web page. A computer-implemented method comprising:
The computer of claim 1, further comprising means for managing a cookie that passes between the client and a local cache memory and includes a client session identifier (ID) to manage the session. The method performed in
A computer program stored in a computer readable medium having instructions to be executed by a computer, wherein the instructions are:
From the client through the network to execute the steps of receiving a request for Oite web page on the computer to the computer, the web page is associated with a web page template defining one or more components of the web page, the The component refers to different areas of the web page ,
The instructions are
The web page template and page component tag of the web page to execute the step of confirming whether a local cache memory in the computer to computer, each page component defined by the web page template, one or more The page component tag associated with the page component tag identifies where the information in the component should be obtained, the due date information of the component, and binary large object (blob) information, where , Parameters are passed from the server to the component, the parameters are known only to the server ,
The instructions are
Downloading the web page template and page component tag of the web page from the server to the local cache memory over the network if the web page template and page component tag are not in the local cache memory;
Assembling a web page from a page template and a page component tag in the local cache memory;
Turkey computer program is executed and providing the web page to the client in the computer.

Images