JP7351469B1 - Web page providing system, web page providing method, and computer program - Google Patents

Abstract

[Problem] To distribute a web page in which new information is posted one after another more stably than before without incurring too much cost. A web server 2 is provided with web page storage means for storing web page data for displaying web pages. The web server 2 stores a web page stored in the web page storage means after a second event occurs when a first event occurs that may or does affect the configuration of the web page. Regenerate page data. Then, when there is a request from the viewing terminal device 3A, the web page data is transmitted to the viewing terminal device 3A. [Selection diagram] Figure 1

Description

The present invention relates to technology for providing web pages to clients.

There are two main methods for providing web pages using a CMS (Content Management System): dynamic distribution and static distribution.

According to dynamic distribution, each time a client requests a web page, a web page is generated based on information stored in a database at that time and sent to the client. On the other hand, according to static distribution, each time a client requests a web page, the web page is sent to the client, but rather than being generated each time a request is made, a previously generated web page is sent.

Basic WWW technology: Static content and dynamic content, Joetsu University of Education, http://juen-cs.dl.juen.ac.jp/html/www/005/, retrieved on April 30, 2023

Dynamic distribution allows new information to be provided to clients more reliably than static distribution. Therefore, dynamic distribution is particularly preferred as a distribution method for web pages where new information is posted one after another.

However, dynamic distribution places a greater load on the web server when generating web pages than static distribution. Therefore, when access to a website is concentrated, the web server may go down.

Therefore, countermeasures such as increasing the specifications of the web server, increasing the number of web servers, or introducing a load balancing device may be taken.

However, these measures are costly and become over-specified when access is not concentrated.

In view of these problems, it is an object of the present invention to distribute web pages in which new information is posted one after another more stably than before without incurring too much cost.

A web page providing system according to one embodiment of the present invention is a web page providing system that provides web pages, and includes a web page storage means for storing web page data for displaying the web page, and a web page storage means for storing web page data for displaying the web page. Deleting means for deleting the web page data from the web page storage means when an event that may or may affect the configuration occurs; If the data is stored in the web page storage means, the stored web page data is sent to the client; if the data is not stored, the web page data is regenerated and sent to the client. and providing means for storing the web page in the web page storage means .

Preferably, the providing means generates the web page data even if a predetermined period of time has passed since the last occurrence of the event, if the web page data is not stored in the web page storage means. and then store it in the web page storage means.

Alternatively, the predetermined time is set shorter as the frequency of access to the web page is higher.

Alternatively, when the web page data is regenerated by the attribute storage means for storing the generation date and time of the web page data, and the providing means regenerates the web page data, the entire part or a predetermined part of the web page data is regenerated. If the content before and after is different, the generation date and time stored in the attribute storage means is updated to the date and time when the web page data was regenerated, and if the content is the same, the management unit does not update the generation date and time. and the providing means is configured to provide the web page data when the cache date and time of the web page data presented by the client at the time of the request is older than the generation date and time stored in the attribute storage means. The page data is sent, and if the page data is new, a message indicating that the web page has not been updated is sent instead of the web page data.

The web page is a fixed page having a list showing one or more article pages associated with at least one of one or more predetermined categories , and the event is An article page that is associated with at least one common category with the web page out of one or more predetermined categories is updated, deleted, or newly added.

According to the present invention, web pages on which new information is posted one after another can be distributed more stably than before without much cost.

FIG. 1 is a diagram showing an example of the overall configuration of a web page providing system. It is a diagram showing an example of the hardware configuration of a web server. FIG. 2 is a diagram illustrating an example of a functional configuration of a web server. FIG. 2 is a diagram showing an example of a functional configuration of a website. It is a diagram showing an example of a fixed page. It is a figure showing an example of attribute data. It is a diagram showing an example of a fixed page. It is a diagram showing an example of a fixed page. It is a diagram showing an example of a fixed page. It is a diagram showing an example of a fixed page. It is a diagram showing an example of a fixed page. It is a figure showing an example of an article page. It is a flowchart which shows an example of the flow of fixed page update processing. FIG. 3 is a diagram showing an example of task data. 3 is a flowchart illustrating an example of the flow of request response processing. 3 is a flowchart illustrating an example of the overall processing flow in a web server.

[1. overall structure〕
FIG. 1 is a diagram showing an example of the overall configuration of a web page providing system 1. As shown in FIG. FIG. 2 is a diagram showing an example of the hardware configuration of the web server 2. As shown in FIG.

A web page providing system 1 shown in FIG. 1 is a system for providing various web pages to various viewers, and includes a web server 2, multiple viewing terminal devices 3A (3A1, 3A2,...), The management terminal device 3B (3B1, 3B2, . . . ), a communication line 10, etc.

The web server 2 can communicate with each viewing terminal device 3A and each management terminal device 3B via the communication line 10. As the communication line 10, the Internet, a LAN (Local Area Network) line, a public line, or the like is used.

The web server 2 manages the data of the web page, and delivers the HTML (Hypertext Markup Language) file of the web page to the viewer's viewing terminal device 3A in response to a request from the viewer.

The web server 2 includes a computer main body 21, a display 22a, a keyboard 22b, a pointing device 22c, and the like. As shown in FIG. 2, the computer main body 21 includes a main processor 21a, a RAM (Random Access Memory) 21b, a ROM (Read Only Memory) 21c, an auxiliary storage device 21d, a network adapter 21e, an input/output interface 21f, and a graphic board 21g. It is composed of etc.

The main processor 21a is a processor such as a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit), and executes a program loaded into the RAM 21b.

In addition to the operating system, a web page management application 20 (see FIG. 3) is installed in the ROM 21c or the auxiliary storage device 21d. Web page management application 20 is loaded into RAM 21b and executed by main processor 21a. Other programs are also loaded into the RAM 21b as appropriate and executed by the main processor 21a. As the auxiliary storage device 21d, an HDD (Hard Disk Drive) or an SSD (Solid State Drive) is used. The web page management application 20 will be described in detail later.

The network adapter 21e is a communication device such as a NIC (Network Interface Card) for communicating with the viewing terminal device 3A, the management terminal device 3B, etc. via the communication line 10. The input/output interface 21f is an input/output board compatible with standards such as USB (Universal Serial Bus), and is connected to a keyboard 22b and a pointing device 22c.

The graphic board 21g generates a video signal for displaying a screen and transmits it to the display 22a. Sometimes called a "video board" or "video card." The display 22a is connected to the graphic board 21g, and displays images based on video signals from the graphic board 21g.

The display 22a displays, based on the video signal, a screen for inputting commands or information, a screen showing the results of processing executed by the main processor 21a, and the like.

Keyboard 22b and pointing device 22c are used to enter commands or information.

Returning to FIG. 1, the viewing terminal device 3A is a client for a viewer to view a web page. A computer equipped with a web browser, such as a personal computer, a smartphone, or a tablet computer, is used as the viewing terminal device 3A.

The management terminal device 3B is a client for a website administrator or poster to newly create, edit, or delete a web page. As the management terminal device 3B, a computer equipped with a web browser is used like the viewing terminal device 3A.

[2. Overview of functional configuration of each part]
FIG. 3 is a diagram showing an example of the functional configuration of the web server 2. As shown in FIG. FIG. 4 is a diagram showing an example of the functional configuration of the website 4. As shown in FIG.

The web page management application 20 is software for CMS (Content Management System). According to the web page management application 20, a new fixed page registration section 201, a fixed page file generation section 202, a new article page registration section 203, an article page file generation section 204, a request response section 206, a task management section 205, shown in FIG. Functions such as a fixed content storage section 241, a fixed page file storage section 242, a fixed page attribute storage section 243, an article content storage section 244, an article page file storage section 245, and a task storage section 246 are implemented in the web server 2. These features allow websites to be built and managed.

Hereinafter, using the website 4 of a certain local government 100 configured as shown in FIG. 4 as an example, the processing of each part of the web server 2, the viewing terminal device 3A, and the management terminal device 3B will be explained in order. do. Website 4 is composed of multiple web pages.

These web pages are broadly classified into fixed pages and article pages. The fixed page is a fixed web page, such as a top page of a website, a web page of a website owner's profile, and a web page for inquiries to the website owner. Hereinafter, the fixed page on website 4 will be referred to as "fixed page 5." Further, each fixed page 5 may be described separately as "fixed page 51", "fixed page 52", etc.

On the other hand, an article page is a web page in which news and the like are described. For example, each page of a blog is an example of an article page. Article pages are also generally called "post pages." Hereinafter, the article page on website 4 will be referred to as "article page 6." Further, each article page 6 may be described separately as "article page 61", "article page 62", etc.

[3. Details of each part]
[3.1 Preparation of fixed page 5]
FIG. 5 is a diagram showing an example of a fixed page 50. FIG. 6 is a diagram showing an example of attribute data 7D. FIG. 7 is a diagram showing an example of the fixed page 51. FIG. 8 is a diagram showing an example of the fixed page 52. FIG. 9 is a diagram showing an example of the fixed page 53. FIG. 10 is a diagram showing an example of the fixed page 54. FIG. 11 is a diagram showing an example of the fixed page 55.

The fixed page 5 is registered in the web server 2 as follows based on the operation by the administrator of the website 4. Hereinafter, a method for registering the fixed page 5 will be described using an example in which the administrator uses the management terminal device 3B1.

When a predetermined command is input by the administrator, the management terminal device 3B1 requests the web server 2 for a fixed page template.

Then, the new fixed page registration unit 201 causes the management terminal device 3B1 to display the fixed page template by transmitting the fixed page template file to the management terminal device 3B1. The administrator mainly inputs the following information (1-1) to (1-5) into the displayed template as information regarding the fixed page 5.
(1-1) File name of the HTML file of fixed page 5 (1-2) Title of fixed page 5 (1-3) Tab name and link destination of the tab placed on fixed page 5 (1-4) Fixed page 5 Content to be posted on (1-5) Category name of article category listed in article list on fixed page 5

For example, when registering the fixed page 50 shown in FIGS. 4 and 5, the administrator inputs "index.html" as the file name of (1-1). Input the character string of title 50a, ie, "Tozai City Website Top Page" as the title of (1-2).

Further, the administrator inputs the tab names of the tabs 50b1, 50b2, . . . , 50b5, ie, "Sports", "Adults", . These tabs are used as hyperlinks to other fixed pages 5. Further, identification information (file name or URL (Uniform Resource Locator)) for identifying each of the fixed pages 51, 52, . . . , 55 is input as a link destination to be associated with each of the tabs 50b1, 50b2, .

Furthermore, the administrator inputs content composed of text, rich text, images, moving images, hyperlinks, etc. as the content (1-4). In this example, the content 50c is input, which is composed of the rich text "2023 marks the 50th anniversary of the city's incorporation." and five flower images.

Further, as the category name (1-5), the administrator inputs the category name of the category of the article page 6 that is desired to be listed in the article list 50d, out of a plurality of category names prepared in advance. For example, if you want to list article page 6 related to sports, enter the category name "Sports". You can also enter multiple category names. If you want to enter the category names for all categories, you can enter "all" instead of these category names.

When the information of the fixed page 50 is input into the template, fixed page data 7A indicating this information is transmitted from the management terminal device 3B1 to the web server 2. When an image or moving image is input as the content in (1-4), the file of the image or moving image is transmitted as an attached file 7B from the management terminal device 3B1 to the web server 2 together with the fixed page data 7A.

Upon receiving the fixed page data 7A, the new fixed page registration unit 201 stores it in the fixed content storage unit 241. If the fixed page data 7A and the attached file 7B are received together with the attached file 7B, the fixed page data 7A and the attached file 7B are stored in the fixed content storage unit 241 in association with each other.

The fixed page file generation unit 202 generates the HTML file 7C of the fixed page 50 based on the template and fixed page data 7A used when inputting the information of the fixed page 50.

The article list 50d lists the titles of the article pages 6 that are associated with the category names shown in the fixed page data 7A. Each title is a hyperlink, and is associated with a URL to each article page 6. The association of category names with article pages 6 will be explained in "3.2 Posting of article pages 6." Note that the update date or update date and time of the article page 6 may be arranged along with the title.

Then, the fixed page file generation section 202 stores the HTML file 7C in the fixed page file storage section 242 in association with the file name (in this example, "index.html") shown in the fixed page data 7A.

The new fixed page registration unit 201 further generates attribute data 7D and stores it in the fixed page attribute storage unit 243 as shown in FIG. The attribute data 7D shows the following information regarding the fixed page 5 (fixed page 50 in this example). The "file name" is the file name of the HTML file 7C, and the file name shown in the fixed page data 7A is used. “Generation date and time” is the date and time when the HTML file 7C was generated.

The "hash value" is the hash value of the HTML file 7C. The hash value is calculated using a predetermined hash function h. Note that the hash value is not the hash value of all parts of the HTML file 7C, but the hash value of the part of the content to be presented to the viewer, such as the part enclosed by body tags (<body>, </body>). You can.

By the above processing, registration of the fixed page 50 to the web server 2 is completed. Fixed pages 5 other than fixed page 50, such as fixed page 51 shown in FIG. 7, fixed page 52 shown in FIG. 8, fixed page 53 shown in FIG. 9, fixed page 54 shown in FIG. 10, and fixed page 55 shown in FIG. etc. are also registered in the web server 2 in a similar manner.

Note that the administrator does not need to input all of (1-1) to (1-5) at once, and may input them several times. In this case, the information input first is stored in the fixed content storage unit 241 as the fixed page data 7A, and the information input after that is added to the fixed page data 7A. Further, each of the information (1-3) to (1-5) may be input as desired. For example, in a case where no article list is provided, such as on the fixed page 55, there is no need to input the category name (1-5). Alternatively, if no tag is provided, such as in fixed pages 54 and 55, there is no need to input the tag name and link destination in (1-3).

[3.2 Posting article page 6]
FIG. 12 is a diagram showing an example of the article page 61.

In the local government 100, posters are determined for each department, and each poster posts articles related to his or her own department as appropriate. For example, a poster in the sports section posts articles about sports tournaments, articles about sports facilities, and the like. Then, the article is registered in the web server 2 as an article page 6.

Hereinafter, a method for registering the article page 6 will be described using an example in which a certain poster uses the management terminal device 3B2.

When a predetermined command is input by the poster, the management terminal device 3B2 requests the web server 2 for a template for the article page.

Then, the new article page registration unit 203 causes the management terminal device 3B2 to display the article page template by transmitting the article page template file to the management terminal device 3B2. The poster mainly inputs the following information (2-1) to (2-3) into the displayed template as information regarding the article page 6.
(2-1) Title of article page 6 (2-2) Content to be posted on article page 6 (2-3) Category name of category of article page 6

For example, when registering the article page 61 shown in FIGS. 4 and 12, the poster inputs the character string of the title 61a, ie, "2023 Marathon Tournament" as the title (2-1). As the content (2-2), content composed of text, rich text, images, moving images, hyperlinks, etc. is input. In this example, content 61b is input that is composed of an illustration of a marathon and rich text consisting of four lines of character strings with different font sizes.

Further, as the category name (2-3), the poster inputs the category name of the category of the article page 61 from among the plurality of category names prepared in advance. Since the article page 61 is about a marathon event, the category name "Sports" may be entered, and since the article page 61 is about an event to be held in 2023, the category name "2023" may be entered. You may enter multiple category names.

When the information of the article page 61 is input into the template, article page data 7E indicating this information is transmitted from the management terminal device 3B2 to the web server 2. If an image or moving image is input as the content in (2-2), the file of the image or moving image is sent as an attached file 7F from the management terminal device 3B1 to the web server 2 together with the article page data 7E.

Upon receiving the article page data 7E, the new article page registration section 203 stores it in the article content storage section 244. When received together with the attached file 7F, the article page data 7E and the attached file 7F are stored in the article content storage unit 244 in association with each other.

The article page file generation unit 204 generates the HTML file 7G of the article page 61 based on the template used when inputting the information of the article page 61, the article page data 7E of the article page 61, and the like. Furthermore, a unique file name (in this example, "000001.html") is issued. Then, the HTML file 7G is stored in the article page file storage unit 245 in association with the published file name.

Through the above processing, registration (posting) of the article page 61 to the web server 2 is completed. Each article page 6 (62, 63, . . . ) other than the article page 61 is also registered in the web server 2 by the same method.

[3.3 Update of fixed page 5]
FIG. 13 is a flowchart illustrating an example of the flow of fixed page update processing. FIG. 14 is a diagram showing an example of task data 7J.

When the article page 6 is updated, deleted, or newly registered, one of the registered fixed pages 5 (see FIG. 4) is regenerated. Hereinafter, the process of regenerating the fixed page 5 will be described with reference to the flowchart of FIG. 13, taking as an example the case where the article page 61 is newly registered.

When an article page 61 is newly registered, the task management unit 205 selects one associated with the category name of the article page 61 from among the registered fixed pages 5 (#801 in FIG. 13). Note that the category name associated with each fixed page 5 is shown in the fixed page data 7A of each fixed page 5.

Then, the task management unit 205 deletes the HTML file 7C of the selected fixed page 5 from the fixed page file storage unit 242 (#802), and generates the task data 7J of the fixed page 5, as shown in FIG. is stored in the task storage unit 246 (#803).

The task data 7J shows the following information. “File name” is identification information (file name or URL) of the fixed page 5. The "scheduled regeneration time" is the scheduled time to start regenerating the HTML file 7C of the fixed page 5, and is the time when the HTML file 7C is deleted plus the predetermined waiting time T. . For example, if the deleted time is "15:59:57" and the waiting time T is "30 seconds", the scheduled reproduction time is "16:00:27".

Note that when the task management unit 205 selects a plurality of fixed pages 5 in step #801, the task management unit 205 deletes each HTML file 7C from the fixed page file storage unit 242 in step #802, and deletes each of the fixed pages 5 in step #803. Data 7J is generated and stored in the task storage unit 246. As shown in FIG. 4, in this example, the category names associated with the article page 61 are "Sports" and "2023", so the fixed page 50, "Sports", which is associated with all category names, is associated with the article page 61. At least three of the fixed page 51 associated with the fixed page 51 and the fixed page 54 associated with "2023" are selected in step #801. Then, each HTML file 7C is deleted from the fixed page file storage section 242, and each task data 7J is generated and stored in the task storage section 246.

The waiting time T may be different for each fixed page 5. For example, the waiting time T of fixed pages 5 that are accessed less frequently may be set longer than the waiting time T of fixed pages 5 that are accessed more frequently.

Further, the task storage unit 246 has the role of a queue. The task data 7J stored in the task storage unit 246 may be sorted in descending order of scheduled regeneration time.

As described above, the fixed page file generation unit 202 generates the HTML file 7C when the fixed page data 7A is sent from the management terminal device 3B, but also generates the HTML file 7C from the task data stored in the task storage unit 246. 7J, the HTML file 7C is generated at the following timing.

When the current time reaches the scheduled regeneration time indicated in a certain task data 7J (Yes in #804), the fixed page file generation unit 202 generates an HTML file 7C of the fixed page 5 corresponding to the task data 7J. The task data 7J is then stored again in the fixed page file storage section 242 (#806), and the task data 7J is deleted from the task storage section 246 (#807).

According to the regenerated HTML file 7C, in the article list of the fixed page 5, the titles of the article pages 6 of the category with the category name associated with the fixed page 5 are arranged as hyperlinks. These article pages 6 include the title of the new article page 6.

Further, the fixed page 5 corresponding to any task data 7J may be requested from the viewing terminal device 3A, but as described above, the HTML file 7C of the fixed page 5 has been deleted. Therefore, when such a fixed page 5 is requested (Yes in #805), the HTML file 7C of the fixed page 5 is regenerated and stored in the fixed page file storage unit 242 (#806), The task data 7J of the fixed page 5 is deleted from the task storage section 246 (#807).

That is, when a new article page 6 is registered, the HTML file 7C of the fixed page 5 related to the new article page 6 is deleted from the fixed page file storage section 242. Then, when a predetermined period of time has passed or the fixed page 5 is requested from the viewing terminal device 3A, the HTML file 7C of the fixed page 5 is regenerated and stored in the fixed page file storage section 242. . The fixed page 5 is updated by such processing.

Further, the fixed page file generation unit 202 generates a hash value of the regenerated HTML file 7C using the hash function h (#808). If the generated hash value and the hash value shown in the attribute data 7D of the fixed page 5 do not match (No in #809), the generation date and time and the hash value shown in the attribute data 7D are The HTML file 7C is updated to the date and time of regeneration and the generated hash value (#810). On the other hand, if the two match (Yes in #809), updating of the attribute data 7D is skipped.

Incidentally, before the HTML file 7C of a certain fixed page 5 is regenerated, some article page 6 may be further updated, deleted, or newly registered. If the category name associated with the article page 6 is also associated with the fixed page 5 (Yes in #811), the task management unit 205 regenerates the task data 7J of the fixed page 5. The scheduled time is updated to the current time plus the waiting time T (#812). As a result, generation of the HTML file 7C for the fixed page 5 is postponed.

For example, at the time of 16:33:20, the scheduled regeneration time indicated in the task data 7J of a certain fixed page 5 is "16:33:27", a new article page 6 is registered, and the article page If the category name associated with 6 is also associated with that fixed page 5, and the waiting time T of that fixed page 5 is "45 seconds", the task management unit 205 The task data 7J is updated so that the scheduled time is shown as "16:34:12".

The processes in steps #804 to #812 are executed for each fixed page 5 in which the task data 7J was registered in step #803.

[3.4 Provision of fixed page 5 and article page 6]
FIG. 15 is a flowchart showing an example of the flow of request response processing.

A viewer can view the fixed page 5 and article page 6 by operating the viewing terminal device 3A. Hereinafter, a method for providing the fixed page 5 and the article page 6 will be described, taking as an example a case where a certain viewer operates the viewing terminal device 3A1.

The viewing terminal device 3A1 transmits the request data 7K to the web server 2 when the URL of any fixed page 5 is specified by the viewer. An example in which the URL of the fixed page 50 is specified will be described below.

The request data 7K shows identification information (eg, file name) of the fixed page 5, ie, the fixed page 50, to which the URL is specified. If the HTML file 7C of the fixed page 50 is cached in the viewing terminal device 3A1, the date and time when the HTML file 7C was acquired (cache date and time) is further included in the request data as the value of "If-Modified-Since". 7K.

When the request response unit 206 receives the request data 7K from the viewing terminal device 3A1, it executes the process of responding to the request data 7K according to the procedure shown in the flowchart of FIG. 15.

The request response unit 206 determines that the HTML file 7C of the fixed page 5 (fixed page 50 in this example) corresponding to the identification information indicated in the request data 7K is stored in the fixed page file storage unit 242 (Yes in #821). ), and if the generation date and time indicated in the attribute data 7D of the fixed page 50 is later than the cache date and time indicated in the request data 7K (Yes in #822), the HTML file 7C is sent to the viewing terminal device 3A1. Send (#823). In other words, perform static distribution.

The viewing terminal device 3A1 then displays the fixed page 50 based on the transmitted HTML file 7C. Note that if the HTML file 7C shows a link to the attached file 7B, the viewing terminal device 3A1 requests the attached file 7B from the web server 2. Then, the request response unit 206 transmits the attached file 7B to the viewing terminal device 3A1. The viewing terminal device 3A1 then displays the image or moving image portion of the fixed page 50 based on the attached file 7B.

On the other hand, if the generation date and time is earlier than the cache date and time (No in #822), instead of the HTML file 7C, a "304 Not Modified" message, i.e., response data indicating that it has not been updated. 7L to the viewing terminal device 3A1 (#824).

When the viewing terminal device 3A1 receives the response data 7L, it displays the fixed page 50 based on the HTML file 7C cached by itself. When the HTML file 7C shows a link to the attached file 7B, the image or moving image portion of the fixed page 50 is displayed based on the attached file 7B cached by itself.

Alternatively, if the HTML file 7C is not stored in the fixed page file storage unit 242 (No in #821), there is a possibility that it was once deleted in order to be regenerated, as explained in step #802 of FIG. be. Therefore, the request response unit 206 performs dynamic distribution as follows.

The request response unit 206 immediately instructs the fixed page file generation unit 202 to regenerate the HTML file 7C (#825). Then, as described in step #805 of FIG. 13, the fixed page file generation unit 202 regenerates the HTML file 7C and stores it in the fixed page file storage unit 242. As a result, the HTML file 7C is updated.

Then, the request response unit 206 transmits the updated (regenerated) HTML file 7C to the viewing terminal device 3A1 (#826).

Then, the viewing terminal device 3A1 displays the fixed page 50 based on the HTML file 7C. Note that if the HTML file 7C shows a link to the attached file 7B, it may be obtained from the web server 2, or if it is cached by itself, this may be used.

When any title is selected from the article list 50d of the fixed page 50, the viewing terminal device 3A1 requests the web server 2 for the article page 6 corresponding to the selected title.

Upon receiving the request, the request response unit 206 transmits the HTML file 7G of the article page 6 to the viewing terminal device 3A1.

The viewing terminal device 3A1 then displays the article page 6 based on the HTML file 7G. Note that if the HTML file 7G shows a link to the attached file 7F, the viewing terminal device 3A1 requests the attached file 7F from the web server 2. Then, the request response unit 206 transmits the attached file 7F to the viewing terminal device 3A1. The viewing terminal device 3A1 then displays the image or moving image portion of the article page 6 based on the attached file 7F.

[4. Overall processing flow and effects of this embodiment]
FIG. 16 is a flowchart showing an example of the overall processing flow in the web server 2. As shown in FIG.

Next, the overall processing flow of the web server 2 will be explained with reference to the flowchart of FIG. 16. Here, the case where a fixed page 51 (see FIGS. 4 and 7) is registered or provided will be explained as an example.

When the web server 2 receives the fixed page data 7A of the fixed page 51, the web server 2 performs a process of generating an HTML file 7C and attribute data 7D of the fixed page 51 as a process of registering the fixed page 51 (#11 in FIG. 16). ).

If there is a command regarding article page 6 (Yes in #12), processing regarding that article page 6 is performed (#13). For example, when article page data 7E of a new article page 6 is received, processing for registering the article page 6 is performed. Alternatively, when there is a command to update an existing article page 6, the article page data 7E of the article page 6 is updated, and the HTML file 7G of the article page 6 is regenerated. Alternatively, if there is a command to delete an existing article page 6, the article page data 7E, HTML file 7G, etc. of the article page 6 are deleted.

Then, the web server 2 executes the fixed page update process described in FIG. 13 (#14).

That is, if the category name associated with the updated, deleted, or newly registered article page 6 is also associated with the fixed page 51, the web server 2 updates the HTML of the fixed page 51. File 7C is temporarily deleted (#802 in FIG. 13). Then, when the scheduled regeneration time comes (Yes in #804) or when the fixed page 51 is requested from the viewing terminal device 3A (Yes in #805), the HTML file 7C is generated again (#806). Before the HTML file 7C is regenerated, any article page 6 is updated, deleted, or newly registered, and the category name associated with that article page 6 is also associated with the fixed page 51. If so (Yes in #811), the scheduled regeneration time is updated to the current time plus the waiting time T (#812). Further, if the hash value of the HTML file 7C deleted in step #802 and the hash value of the HTML file 7C regenerated in #806 do not match (No in #809), the attribute data 7D of the fixed page 51 (see FIG. ) is updated to indicate the generation date and time and hash value of the regenerated HTML file 7C (#810).

Alternatively, if the viewing terminal device 3A requests data indicating the identification information of the fixed page 51 as the request data 7K (Yes in #15 of FIG. 16), the web server 2 performs the request response process described in FIG. Execute (#16).

That is, the web server 2 stores the HTML file 7C of the fixed page 51 (Yes in #821 in FIG. 15), and the generation date and time indicated in the attribute data 7D of the fixed page 51 is indicated in the request data 7K. If it is later than the cache date and time (Yes in #822), the HTML file 7C is sent to the viewing terminal device 3A (#823). In other words, perform static distribution. If the generation date and time is earlier than the cache date and time (No in #822), data indicating the message "304 Not Modified", that is, response data 7L, is transmitted to the viewing terminal device 3A (#824). If the HTML file 7C is not stored, the fixed page update process immediately regenerates the HTML file 7C (see #806 in FIG. 13), and sends it to the viewing terminal device 3A (#826). In other words, dynamic distribution is performed.

While continuing the service, the web server 2 appropriately executes the processes of steps #12 to #16 in FIG. 16 depending on the event that occurs. Further, fixed pages 5 other than fixed page 51 are also processed in the same manner.

According to this embodiment, the web server 2 basically provides the HTML file 7C of the fixed page 5 by static distribution. Furthermore, when there is a possibility that the configuration of the fixed page 5 may change due to addition, update, or deletion of the article page 6, the HTML file 7C of the fixed page 5 is temporarily deleted. If there is a request for the fixed page 5 by the waiting time T, the HTML file 7C is generated again and the HTML file 7C is provided. In other words, the HTML file 7C is provided by dynamic distribution. On the other hand, if there is no request for the fixed page 5 by the waiting time T, the HTML file 7C is regenerated and prepared for static distribution. With such a distribution method, the fixed page 5 can be distributed in a new state more stably than before without incurring much cost.

Additionally, while waiting for the fixed page 5 to be regenerated, if an article page 6 that has the same category name as the fixed page 5 is updated, deleted, or newly generated, the web server 2 will reproduce the fixed page 5. Extend the waiting period by resetting the scheduled completion time. Thereby, the number of times the HTML file 7C is generated can be reduced overall, and further stability can be achieved.

[5. Modified example]
In this embodiment, when an article page 6 is added, updated, or deleted, the web server 2 stores the task data 7J of the fixed page 5 associated with the category name of the article page 6 in the task storage. 246 (see FIG. 14), and the HTML file 7C of the fixed page 5 is deleted from the fixed page file storage section 242, but the same process may be performed when another event occurs. Even when a fixed part of the fixed page 5 (for example, the title 50a, tabs 50b1 to 50b5, or content 50c shown in FIG. 5) is edited, the task data 7J of the fixed page 5 is registered and the fixed page is edited. The HTML file 7C of 5 may be deleted.

As described above, the hash values of the HTML file 7C of the fixed page 5 may be the same before and after regeneration. In other words, even if it is regenerated, the configuration of the fixed page 5 may not substantially change. Therefore, before registering the response data 7L and deleting the HTML file 7C, the web server 2 may determine whether the configuration of the fixed page 5 will change by regenerating it. Then, the response data 7L may be registered and the HTML file 7C may be deleted only when the configuration changes. Note that whether or not the configuration changes may be determined based on whether or not the members of the article list (for example, the article list 50d of the fixed page 50 shown in FIG. 5) change.

In the present embodiment, the web server 2 regenerates the HTML file 7C at the regeneration scheduled time indicated in the task data 7J, but if there is sufficient resources (for example, if the usage rate of the main processor 21a is ), the HTML file 7C may be regenerated without waiting for the scheduled regeneration time. If there is a plurality of task data 7J, the task data 7J may be regenerated preferentially starting from the one with the earliest scheduled regeneration time.

In this embodiment, the explanation has been given by taking as an example the regeneration and provision of the HTML file 7C of the fixed page 5 having the article list of the article page 6, but the regeneration and provision of the HTML file of other fixed pages (web pages) is also possible. , the present invention can be applied. For example, the present invention can be applied to regenerating and providing a web page that has a timeline and broadcasts sports in real time.

In this embodiment, the respective means shown in FIG. 3 are collectively provided in the web server 2, but they may be provided in a distributed manner in a plurality of devices.

In addition, the overall configuration of the web page providing system 1 and the web server 2 or the configuration of each part, the content of processing, the order of processing, the data configuration, etc. can be changed as appropriate in accordance with the spirit of the present invention.

2 Web server 202 Web page file generation unit (generation means, management means)
205 Task management section (deletion means)
206 Request response unit (transmission means)
5 Fixed page (web page)
6 Article page 242 Fixed page file storage unit 243 Fixed page attribute storage unit (attribute storage means)
3A Viewer terminal device (client)
7C HTML file

Claims (7)

A web page providing system that provides web pages,
web page storage means for storing web page data for displaying the web page;
Deleting means for deleting the web page data from the web page storage means when an event that may or does affect the configuration of the web page occurs;
When a request is received from a client, if the web page data is stored in the web page storage means, the stored web page data is sent to the client, and if not stored, the web page data is sent to the client. Providing means for regenerating web page data and transmitting it to the client and storing it in the web page storage means;
A web page providing system comprising: The providing means may generate the web page data again even if a predetermined time has elapsed since the last occurrence of the event, if the web page data is not stored in the web page storage means. storing it in the web page storage means;
The web page providing system according to claim 1. The predetermined time is set shorter as the frequency of access to the web page is higher;
The web page providing system according to claim 2. attribute storage means for storing the generation date and time of the web page data;
When the web page data is regenerated by the providing means, if the content of all or a predetermined part of the web page data before and after the regeneration is different, it is stored in the attribute storage means. A management means that updates the generation date and time to the date and time when the web page data was regenerated, and does not update the generation date and time if they are the same;
has
The providing means transmits the web page data when the cache date and time of the web page data presented by the client at the time of the request is older than the generation date and time stored in the attribute storage means, If the web page is new, a message indicating that the web page has not been updated is sent instead of the web page data;
A web page providing system according to any one of claims 1 to 3. The web page is a fixed page having a list showing one or more article pages associated with at least one of one or more predetermined categories ,
The event is that an article page that is associated with at least one common category with the web page among the one or more predetermined categories is updated, deleted, or newly added. is,
A web page providing system according to any one of claims 1 to 3. A web page providing method for providing a web page, the method comprising:
Prepare a web page storage means for storing web page data for displaying the web page,
deleting the web page data from the web page storage means when an event that may or does affect the configuration of the web page occurs;
When a request is received from a client, if the web page data is stored in the web page storage means, the stored web page data is sent to the client, and if not stored, the web page data is sent to the client. Regenerating web page data and transmitting it to the client and storing it in the web page storage means;
A web page providing method characterized by: A computer program for use in a computer that provides a web page by transmitting web page data for displaying the web page stored in a web page storage means, the computer program comprising:
to the computer;
executing a process of deleting the web page data from the web page storage means when an event that may or does affect the configuration of the web page occurs;
When a request is received from a client, if the web page data is stored in the web page storage means, a process is executed to transmit the stored web page data to the client, and if the web page data is not stored. If so, regenerate the web page data, transmit it to the client, and cause the web page storage means to store the data.
A computer program characterized by:

Images