Webpage provision system, webpage provision method, and computer program
Patent Information
- Application Number
- JP2023078784
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-11
- Publication Date
- 2024-11-21
- Estimated Expiration
- 2043-05-11
AI Technical Summary
【0015】 本発明によると、コストをあまり掛けることなく従来よりも安定的に、新しい情報が次々に掲載されるウェブページを配信することができる。
Smart Images

Figure 2024162849000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a technique for providing a web page to a client. [Background technology]
[0002] There are two main ways for a CMS (Content Management System) to provide web pages: dynamic delivery and static delivery.
[0003] With dynamic delivery, each time a web page is requested by a client, a web page is generated based on the information stored in the database at that time and sent to the client. On the other hand, with static delivery, each time a web page is requested by a client, the web page is sent to the client, but a pre-generated one is sent rather than being generated each time a request is made. [Prior art documents] [Non-patent literature]
[0004] [Non-Patent Document 1] Basic Technology of WWW: Static and Dynamic Content, Joetsu University of Education, http: / / juen-cs.dl.juen.ac.jp / html / www / 005 / , retrieved April 30, 2023 Summary of the Invention [Problem to be solved by the invention]
[0005] Dynamic delivery can provide new information to clients more reliably than static delivery, and is therefore preferred as a delivery method for web pages, in particular, where new information is constantly being posted.
[0006] However, dynamic delivery places a heavier load on the web server when generating web pages than static delivery, and therefore the web server may go down if there is a high volume of access to the website.
[0007] In response, measures may be taken such as upgrading the specifications of the web server, increasing the number of web servers, or introducing a load balancing device.
[0008] However, these measures are costly and can be overkill when there is not a lot of traffic.
[0009] In view of the above problems, the present invention has an object to distribute web pages on which new information is continuously posted more stably than before without incurring too much cost. [Means for solving the problem]
[0010] A webpage providing system according to one embodiment of the present invention is a webpage providing system that provides a webpage, and includes a webpage storage means for storing webpage data for displaying the webpage, a generation means for regenerating the webpage data stored in the webpage storage means after a second event occurs when a first event occurs that may affect or does affect the configuration of the webpage, and a transmission means for transmitting the webpage data to a client when requested by the client.
[0011] Preferably, the system further comprises a deletion means for deleting the web page data from the web page storage means when the first event occurs, and the second event is when the request is made from the client when the web page data is not stored in the web page storage means, or when a predetermined time has elapsed since the first event last occurred.
[0012] Alternatively, the predetermined time is set to be shorter as the frequency of access to the web page increases.
[0013] Alternatively, the system may include an attribute storage means for storing the generation date and time of the web page data, and a management means for updating the generation date and time stored in the attribute storage means to the date and time when the web page data was regenerated by the generation means if the contents of all or a specified part of the web page data before and after regeneration are different, and not updating the generation date and time if they are identical, and the transmission means transmits the web page data if the cache date and time of the web page presented by the client at the time of the request is older than the generation date and time stored in the attribute storage means, and if it is newer, transmits a message indicating that the web page has not been updated instead of the web page data.
[0014] Alternatively, the web page is a static page having a list of one or more article pages, and the first event is an article page that is associated with a common category name as the web page being updated, deleted, or newly added. Effect of the Invention
[0015] According to the present invention, it is possible to distribute web pages on which new information is continually posted more stably than before without incurring significant costs. [Brief description of the drawings]
[0016] [Figure 1] FIG. 1 illustrates an example of an overall configuration of a web page providing system. [Diagram 2] FIG. 2 illustrates an example of a hardware configuration of a web server. [Diagram 3] FIG. 2 is a diagram illustrating an example of a functional configuration of a web server. [Figure 4] FIG. 2 is a diagram illustrating an example of a functional configuration of a website. [Diagram 5]FIG. 13 is a diagram illustrating an example of a static page. [Figure 6] FIG. 11 is a diagram illustrating an example of attribute data. [Figure 7] FIG. 13 is a diagram illustrating an example of a static page. [Figure 8] FIG. 13 is a diagram illustrating an example of a static page. [Figure 9] FIG. 13 is a diagram illustrating an example of a static page. [Figure 10] FIG. 13 is a diagram illustrating an example of a static page. [Figure 11] FIG. 13 is a diagram illustrating an example of a static page. [Figure 12] FIG. 13 is a diagram illustrating an example of an article page. [Figure 13] 13 is a flowchart showing an example of the flow of a fixed page update process. [Figure 14] FIG. 11 is a diagram illustrating an example of task data. [Figure 15] 13 is a flowchart showing an example of the flow of a request response process. [Figure 16] 11 is a flowchart showing an example of an overall processing flow in a web server. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0017] [1. Overall structure] Fig. 1 is a diagram showing an example of the overall configuration of a web page providing system 1. Fig. 2 is a diagram showing an example of the hardware configuration of a web server 2.
[0018] The web page providing system 1 shown in Figure 1 is a system for providing various web pages to various viewers, and is composed of a web server 2, a plurality of viewing terminal devices 3A (3A1, 3A2, ...), a plurality of management terminal devices 3B (3B1, 3B2, ...), and a communication line 10.
[0019] The web server 2 can communicate with each viewing terminal device 3A and each management terminal device 3B via a communication line 10. As the communication line 10, the Internet, a LAN (Local Area Network) line, a public line, or the like is used.
[0020] The web server 2 manages web page data, and delivers HTML (Hypertext Markup Language) files of the web pages and the like to the browsing terminal device 3A of the viewer in response to a request from the viewer.
[0021] The web server 2 is composed of a computer main body 21, a display 22a, a keyboard 22b, a pointing device 22c, etc. As shown in Fig. 2, the computer main body 21 is composed of 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, etc.
[0022] The main processor 21a is a processor such as a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit), and executes programs loaded into the RAM 21b.
[0023] 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. The web page management application 20 is loaded into the RAM 21b and executed by the main processor 21a. Other programs are also loaded into the RAM 21b as appropriate and executed by the main processor 21a. A hard disk drive (HDD) or a solid state drive (SSD) is used as the auxiliary storage device 21d. The web page management application 20 will be described in detail later.
[0024] The network adapter 21e is a communication device such as a network interface card (NIC) for communicating with the viewing terminal device 3A and the management terminal device 3B via the communication line 10. The input / output interface 21f is an input / output board conforming to standards such as Universal Serial Bus (USB), and is connected to a keyboard 22b and a pointing device 22c.
[0025] The graphic board 21g generates a video signal for displaying a screen and transmits it to the display 22a. It is also called a "video board" or a "video card." The display 22a is connected to the graphic board 21g and displays an image based on the video signal from the graphic board 21g.
[0026] The display 22a displays, based on the video signal, a screen for inputting commands or information, a screen showing the results of processing performed by the main processor 21a, and the like.
[0027] The keyboard 22b and pointing device 22c are used to enter commands or information.
[0028] 1, the viewing terminal device 3A is a client for a viewer to view a web page. As the viewing terminal device 3A, a computer equipped with a web browser, such as a personal computer, a smartphone, or a tablet computer, is used.
[0029] The management terminal device 3B is a client that allows a website administrator or contributor to create, edit, or delete a web page. As the management terminal device 3B, a computer equipped with a web browser is used, similar to the browsing terminal device 3A.
[0030] [2. Overview of the Functional Configuration of Each Part] Fig. 3 is a diagram showing an example of the functional configuration of the web server 2. Fig. 4 is a diagram showing an example of the functional configuration of the website 4.
[0031] The web page management application 20 is software for a CMS (Content Management System). According to the web page management application 20, functions such as a new static page registration unit 201, a static page file generation unit 202, a new article page registration unit 203, an article page file generation unit 204, a request response unit 206, a task management unit 205, a fixed content storage unit 241, a static page file storage unit 242, a static page attribute storage unit 243, an article content storage unit 244, an article page file storage unit 245, and a task storage unit 246 shown in Fig. 3 are realized in the web server 2. A website is constructed and managed by these functions.
[0032] The following describes the processing of each part of the web server 2, the browsing terminal device 3A, and the management terminal device 3B, taking as an example the website 4 of a certain local government 100, configured as shown in Figure 4. The website 4 is made up of multiple web pages.
[0033] These web pages are broadly classified into static pages and article pages. Static pages are fixed web pages such as the top page of a website, a web page with the website owner's profile, and a web page for inquiries to the website owner. Hereinafter, a static page in website 4 will be referred to as "static page 5." In addition, each static page 5 may be distinguished and described as "static page 51," "static page 52," ...
[0034] On the other hand, an article page is a webpage that contains news and the like. For example, each page of a blog is an example of an article page. Article pages are also commonly called "post pages." Below, an article page on website 4 will be referred to as "article page 6." Additionally, each article page 6 may be distinguished and referred to as "article page 61," "article page 62," ...
[0035] [3. Details of each part] [3.1 Preparation of Static Page 5] FIG. 5 is a diagram showing an example of a static page 50. FIG. 6 is a diagram showing an example of attribute data 7D. FIG. 7 is a diagram showing an example of a static page 51. FIG. 8 is a diagram showing an example of a static page 52. FIG. 9 is a diagram showing an example of a static page 53. FIG. 10 is a diagram showing an example of a static page 54. FIG. 11 is a diagram showing an example of a static page 55.
[0036] Static page 5 is registered in web server 2 as follows, based on the operation of the administrator of website 4. Below, a method of registering static page 5 will be explained, taking as an example a case where the administrator uses management terminal device 3B1.
[0037] When a prescribed command is input by the administrator, the management terminal device 3B1 requests the web server 2 for a template for a static page.
[0038] Then, the new static page registration unit 201 transmits a file of the template for the static page to the management terminal device 3B1, thereby causing the management terminal device 3B1 to display the template for the static page. The administrator inputs the following information (1-1) to (1-5) into the displayed template as information about the static page 5. (1-1) File name of the HTML file for static page 5 (1-2) Title of static page 5 (1-3) Tab name and link destination of the tab to be placed on static page 5 (1-4) Content to be posted on static page 5 (1-5) Category name of the article category to be listed in the article list of static page 5 For example, when registering the static page 50 shown in Figures 4 and 5, the administrator inputs "index.html" as the file name of (1-1) and the character string of the title 50a, i.e., "Tozai City Website Top Page," as the title of (1-2).
[0039] Furthermore, the administrator inputs the tab names of the tabs 50b1, 50b2, ..., 50b5, i.e., "Sports", "Adult", ..., and "Access", as the tab names of (1-3). These tabs are used as hyperlinks to other static pages 5. In addition, the administrator inputs identification information (file names or URLs (Uniform Resource Locators)) that identifies the static pages 51, 52, ..., 55, respectively, as link destinations to be associated with the tabs 50b1, 50b2, ..., 50b5, respectively.
[0040] Furthermore, the administrator inputs, as the content (1-4), content consisting of text, rich text, images, video, hyperlinks, etc. In this example, the administrator inputs content 50c consisting of rich text "The year 2023 marks the 50th anniversary of the city's establishment" and images of five flowers.
[0041] Furthermore, the administrator inputs, as the category name (1-5), from among multiple category names prepared in advance, the category name of the category of article pages 6 that the administrator wishes to list in the article list 50d. For example, if the administrator wishes to list article pages 6 related to sports, the administrator inputs the category name "sports." It is also possible to input multiple category names. When inputting the category names of all categories, the administrator may input "all" instead of these category names.
[0042] When information on static page 50 is entered into the template, static page data 7A indicating this information is transmitted from management terminal device 3B1 to web server 2. When an image or video is input as the content of (1-4), the file of that image or video is transmitted as an attached file 7B from management terminal device 3B1 to web server 2 together with static page data 7A.
[0043] When the new fixed page registration unit 201 receives the fixed page data 7A, it stores it in the fixed content storage unit 241. When it receives the fixed page data 7A together with the attached file 7B, it stores the fixed page data 7A and the attached file 7B in the fixed content storage unit 241 in association with each other.
[0044] The static page file generating unit 202 generates an HTML file 7C of the static page 50 based on the template used when inputting the information of the static page 50, the static page data 7A, and the like.
[0045] The article list 50d lists the titles of the article pages 6 associated with the category names indicated in the static page data 7A. Each title is a hyperlink, and is associated with a URL to the respective article page 6. The association of category names with article pages 6 will be explained in "3.2 Posting an article page 6." The update date or update time of the article page 6 may be listed together with the title.
[0046] Then, the static page file generating unit 202 stores the HTML file 7C in the static page file storage unit 242 in association with the file name (in this example, "index.html") indicated in the static page data 7A.
[0047] The new static page registration unit 201 further generates attribute data 7D and stores it in the static page attribute storage unit 243 as shown in FIG. 6. The attribute data 7D indicates the following information about the static page 5 (in this example, static page 50): "File name" is the file name of the HTML file 7C, and the file name indicated in the static page data 7A is used. "Created date and time" is the date and time when the HTML file 7C was created.
[0048] 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 does not have to be the hash value of the entire HTML file 7C, but may be the hash value of only a portion of the content to be presented to the viewer, such as the portion enclosed in the body tag (,).
[0049] The above process completes the registration of the static page 50 to the web server 2. Static pages 5 other than the static page 50, such as the static page 51 shown in Fig. 7, the static page 52 shown in Fig. 8, the static page 53 shown in Fig. 9, the static page 54 shown in Fig. 10, and the static page 55 shown in Fig. 11, are also registered to the web server 2 in a similar manner.
[0050] The administrator does not need to input all of (1-1) to (1-5) at once, but may input them in several batches. 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 thereafter is added to the fixed page data 7A. Also, each piece of information (1-3) to (1-5) may be input arbitrarily as needed. For example, if an article list is not provided as in the case of the fixed page 55, there is no need to input the category name in (1-5). Or, if a tag is not provided as in the case of the fixed pages 54 and 55, there is no need to input the tag name and link destination in (1-3).
[0051] [3.2 Posting article page 6] FIG. 12 is a diagram showing an example of an article page 61. As shown in FIG.
[0052] In the local government 100, a contributor is assigned to each department, and each contributor posts articles related to his / her department as appropriate. For example, a contributor from the sports department posts articles about sports tournaments and sports facilities. The articles are then registered on the web server 2 as article pages 6.
[0053] Hereinafter, a method for registering an article page 6 will be described, taking as an example a case where a certain contributor uses the management terminal device 3B2.
[0054] When a specific command is input by the poster, the management terminal device 3B2 requests the web server 2 for a template for an article page.
[0055] Then, the new article page registration unit 203 transmits a template file for the article page to the management terminal device 3B2, thereby causing the management terminal device 3B2 to display the template for the article page. The contributor inputs information about the article page 6, mainly the following information (2-1) to (2-3), into the displayed template. (2-1) Title of article page 6 (2-2) Content to be published on article page 6 (2-3) Category name of article page 6 For example, when registering the article page 61 shown in FIG. 4 and FIG. 12, the contributor inputs the character string of the title 61a, i.e., "2023 Marathon," as the title of (2-1). As the content of (2-2), the contributor inputs content consisting of text, rich text, images, moving images, hyperlinks, etc. In this example, the contributor inputs content 61b consisting of an illustration of a marathon and rich text consisting of four lines of character strings with different font sizes.
[0056] Furthermore, the poster inputs, as the category name of (2-3), the category name of the category of the article page 61 from among multiple category names prepared in advance. Since the article page 61 is about a marathon, the poster may input the category name "Sports," or since the article page 61 is about an event to be held in 2023, the poster may input the category name "2023." Multiple category names may be input.
[0057] When information on article page 61 is entered into the template, article page data 7E indicating this information is transmitted from management terminal device 3B2 to web server 2. When an image or video is input as the content of (2-2), the file of that image or video is transmitted as an attached file 7F from management terminal device 3B1 to web server 2 together with article page data 7E.
[0058] When the new article page registration unit 203 receives the article page data 7E, it stores it in the article content storage unit 244. When it is received together with the attached file 7F, it stores the article page data 7E and the attached file 7F in the article content storage unit 244 in association with each other.
[0059] The article page file generating unit 204 generates an HTML file 7G of the article page 61 based on the template used when inputting the information of the article page 61 and the article page data 7E of the article page 61. It also issues a unique file name (in this example, "000001.html"). Then, it stores the HTML file 7G in the article page file storage unit 245 in association with the issued file name.
[0060] The above process completes the registration (posting) of the article page 61 to the web server 2. Each article page 6 (62, 63, . . . ) other than the article page 61 is also registered to the web server 2 in a similar manner.
[0061] [3.3 Updating Static Page 5] Fig. 13 is a flowchart showing an example of the flow of a static page update process. Fig. 14 is a diagram showing an example of task data 7J.
[0062] When an article page 6 is updated, deleted, or newly registered, one of the registered static pages 5 (see FIG. 4) is regenerated. Below, the process of regenerating the static page 5 will be described with reference to the flowchart in FIG. 13, taking the case where an article page 61 is newly registered as an example.
[0063] When an article page 61 is newly registered, the task management unit 205 selects from the registered static pages 5 those that correspond to the category name of the article page 61 (#801 in FIG. 13). The category name that corresponds to each static page 5 is indicated in the static page data 7A of each static page 5.
[0064] Then, the task management unit 205 deletes the HTML file 7C of the selected static page 5 from the static page file storage unit 242 (#802), and generates task data 7J for the static page 5 and stores it in the task storage unit 246 as shown in FIG. 14 (#803).
[0065] The task data 7J indicates the following information: "File name" is the identification information (file name or URL) of that static page 5. "Scheduled regeneration time" is the scheduled time to start regeneration of the HTML file 7C of that static page 5, which is the time when that HTML file 7C was deleted plus a specified waiting time T. For example, if the deletion time is "15:59:57" and the waiting time T is "30 seconds", then the scheduled playback time is "16:00:27".
[0066] In addition, when the task management unit 205 selects a plurality of static pages 5 in step #801, it deletes each HTML file 7C from the static page file storage unit 242 in step #802, and generates each task data 7J in step #803 and stores it 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 at least three static pages are selected in step #801: the static page 50 associated with all category names, the static page 51 associated with "Sports", and the static page 54 associated with "2023". Then, each HTML file 7C is deleted from the static page file storage unit 242, and each task data 7J is generated and stored in the task storage unit 246.
[0067] The wait time T may be different for each static page 5. For example, the wait time T of a static page 5 that is accessed less frequently may be set to be longer than the wait time T of a static page 5 that is accessed more frequently.
[0068] Furthermore, the task storage unit 246 plays the role of a queue (waiting list). The task data 7J stored in the task storage unit 246 may be rearranged in ascending order of scheduled regeneration time.
[0069] As described above, the fixed page file generation unit 202 generates an HTML file 7C when fixed page data 7A is transmitted from the management terminal device 3B, and further generates an HTML file 7C at the following times based on the task data 7J stored in the task memory unit 246.
[0070] When the current time reaches the scheduled regeneration time indicated in a certain task data 7J (Yes in #804), the static page file generation unit 202 regenerates the HTML file 7C of the static page 5 corresponding to that task data 7J and stores it in the static page file memory unit 242 (#806), and deletes the task data 7J from the task memory unit 246 (#807).
[0071] According to the regenerated HTML file 7C, the titles of the article pages 6 in the category that corresponds to the static page 5 are placed as hyperlinks in the article list of the static page 5. These article pages 6 include the title of the new article page 6.
[0072] Also, a static page 5 corresponding to any of the task data 7J may be requested from the browsing terminal device 3A, but as described above, the HTML file 7C of that static page 5 has been deleted. Therefore, when such a static page 5 is requested (Yes in #805), the HTML file 7C of that static page 5 is similarly generated and stored in the static page file storage unit 242 (#806), and the task data 7J of that static page 5 is deleted from the task storage unit 246 (#807).
[0073] That is, when a new article page 6 is registered, the HTML file 7C of the static page 5 related to that article page 6 is deleted from the static page file storage unit 242. Then, after a predetermined time has passed or when that static page 5 is requested by the browsing terminal device 3A, the HTML file 7C of that static page 5 is regenerated and stored in the static page file storage unit 242. Through this process, the static page 5 is updated.
[0074] Furthermore, the static page file generating unit 202 generates a hash value of the regenerated HTML file 7C using the hash function h (#808). If the generated hash value does not match the hash value indicated in the attribute data 7D of the static page 5 (No in #809), the generation date and time and the hash value indicated in the attribute data 7D are updated to the date and time when the HTML file 7C was regenerated and the generated hash value, respectively (#810). On the other hand, if the two match (Yes in #809), the update of the attribute data 7D is skipped.
[0075] Meanwhile, before the HTML file 7C of a certain static page 5 is regenerated, any article page 6 may be updated, deleted, or newly registered. If the category name associated with the article page 6 is also associated with the static page 5 (Yes in #811), the task management unit 205 updates the scheduled regeneration time of the task data 7J of the static page 5 to the current time plus the waiting time T (#812). This postpones the generation of the HTML file 7C of the static page 5.
[0076] For example, if at 16:33:20 the scheduled regeneration time indicated in the task data 7J of a certain static page 5 is "16:33:27", a new article page 6 is registered, the category name associated with the article page 6 is also associated with the static page 5, and the waiting time T of the static page 5 is "45 seconds", the task management unit 205 updates the task data 7J so that the scheduled regeneration time indicates "16:34:12".
[0077] The processing of steps #804 to #812 is executed for each static page 5 for which the task data 7J was registered in step #803.
[0078] [3.4 Providing static pages 5 and article pages 6] FIG. 15 is a flowchart showing an example of the flow of a request response process.
[0079] A viewer can view the static page 5 and the article page 6 by operating the viewing terminal device 3A. Below, a method for providing the static page 5 and the article page 6 will be described using an example in which a viewer operates the viewing terminal device 3A1.
[0080] When the URL of any one of the static pages 5 is specified by the viewer, the viewing terminal device 3A1 transmits request data 7K to the web server 2. Below, an example will be described in which the URL of the static page 50 is specified.
[0081] The request data 7K indicates identification information (e.g., file name) of the static page 5 whose URL is specified, that is, the static page 50. If the HTML file 7C of the static page 50 is cached in the browsing terminal device 3A1, the request data 7K further indicates the date and time when the HTML file 7C was acquired (cached date and time) as the value of "If-Modified-Since."
[0082] When the request response unit 206 receives the request data 7K from the viewing terminal device 3A1, it executes processing for responding to the request data 7K in accordance with the procedure shown in the flowchart of FIG.
[0083] If the HTML file 7C of the static page 5 (static page 50 in this example) corresponding to the identification information indicated in the request data 7K is stored in the static page file storage unit 242 (Yes in #821), and the generation date and time indicated in the attribute data 7D of the static page 50 is later than the cache date and time indicated in the request data 7K (Yes in #822), the request response unit 206 transmits the HTML file 7C to the viewing terminal device 3A1 (#823). In other words, static distribution is performed.
[0084] The viewing terminal device 3A1 then displays the static page 50 based on the transmitted HTML file 7C. If the HTML file 7C contains a link to the attached file 7B, the viewing terminal device 3A1 requests the attached file 7B from the web server 2. The request response unit 206 then transmits the attached file 7B to the viewing terminal device 3A1. The viewing terminal device 3A1 then displays the image or video portion of the static page 50 based on the attached file 7B.
[0085] On the other hand, if the creation date and time is earlier than the cache date and time (No in #822), then instead of the HTML file 7C, a "304 Not Modified" message, i.e., response data 7L indicating that the file has not been updated, is sent to the viewing terminal device 3A1 (#824).
[0086] When the viewing terminal device 3A1 receives the response data 7L, it displays the static page 50 based on the HTML file 7C that it has cached. If the HTML file 7C contains a link to an attached file 7B, it displays the image or video portion of the static page 50 based on the attached file 7B that it has cached.
[0087] Or, if the HTML file 7C is not stored in the static page file storage unit 242 (No in #821), it may have been deleted temporarily in order to be regenerated, as explained in step #802 of Fig. 13. Therefore, the request response unit 206 performs dynamic delivery as follows.
[0088] The request response unit 206 immediately commands the static page file generation unit 202 to regenerate the HTML file 7C (#825). Then, as explained in step #805 of FIG. 13, the static page file generation unit 202 regenerates the HTML file 7C and stores it in the static page file storage unit 242. This updates the HTML file 7C.
[0089] Then, the request response section 206 transmits the updated (regenerated) HTML file 7C to the viewing terminal device 3A1 (#826).
[0090] Then, the browsing terminal device 3A1 displays the static page 50 based on the HTML file 7C. If the HTML file 7C contains a link to the auxiliary file 7B, the auxiliary file 7B may be obtained from the web server 2, or may be cached by the browsing terminal device 3A1 itself.
[0091] When any title is selected from the article list 50d of the static page 50, the browsing terminal device 3A1 requests the web server 2 for the article page 6 corresponding to the selected title.
[0092] When the request response unit 206 receives the request, it transmits the HTML file 7G of the article page 6 to the browsing terminal device 3A1.
[0093] The viewing terminal device 3A1 then displays the article page 6 based on the HTML file 7G. If the HTML file 7G contains a link to an attached file 7F, the viewing terminal device 3A1 requests the attached file 7F from the web server 2. The request response unit 206 then transmits the attached file 7F to the viewing terminal device 3A1. The viewing terminal device 3A1 then displays the image or video portion of the article page 6 based on the attached file 7F.
[0094] 4. Overall Processing Flow and Effects of This Embodiment FIG. 16 is a flowchart showing an example of the overall process flow in the web server 2.
[0095] Next, the overall process flow of the web server 2 will be described with reference to the flowchart in Fig. 16. In particular, the case where a static page 51 (see Figs. 4 and 7) is registered or provided will be described as an example.
[0096] When the web server 2 receives the static page data 7A of the static page 51, it performs processing for registering the static page 51, such as generating an HTML file 7C and attribute data 7D of the static page 51 (#11 in FIG. 16).
[0097] If there is a command related to an article page 6 (Yes in #12), processing related to that article page 6 is performed (#13). For example, when article page data 7E for a new article page 6 is received, processing is performed to register that article page 6. Alternatively, if there is a command to update an existing article page 6, the article page data 7E for that article page 6 is updated and the HTML file 7G for that article page 6 is regenerated. Alternatively, if there is a command to delete an existing article page 6, the article page data 7E and HTML file 7G for that article page 6 are deleted.
[0098] Then, the web server 2 executes the static page update process explained in FIG. 13 (#14).
[0099] That is, if the category name associated with the updated, deleted, or newly registered article page 6 is also associated with the static page 51, the web server 2 temporarily deletes the HTML file 7C of the static page 51 (#802 in FIG. 13). Then, when the scheduled regeneration time arrives (Yes in #804) or when the static page 51 is requested by the browsing terminal device 3A (Yes in #805), the HTML file 7C is regenerated (#806). If any article page 6 is updated, deleted, or newly registered before the HTML file 7C is regenerated and the category name associated with that article page 6 is also associated with the static page 51 (Yes in #811), the scheduled regeneration time is updated to the current time plus the waiting time T (#812). Furthermore, if the hash value of the HTML file 7C deleted in step #802 does not match the hash value of the HTML file 7C regenerated in #806 (No in #809), the attribute data 7D (see FIG. 6) of the static page 51 is updated to indicate the generation date and time and hash value of the regenerated HTML file 7C (#810).
[0100] Alternatively, if the viewing terminal device 3A requests data indicating the identification information of the static page 51 as request data 7K (Yes in #15 of FIG. 16), the web server 2 executes the request response processing described in FIG. 15 (#16).
[0101] That is, if the web server 2 stores the HTML file 7C of the static page 51 (Yes in #821 of FIG. 15) and the creation date and time indicated in the attribute data 7D of the static page 51 is later than the cache date and time indicated in the request data 7K (Yes in #822), the web server 2 transmits the HTML file 7C to the browsing terminal device 3A (#823). That is, static delivery is performed. If the creation date and time is earlier than the cache date and time (No in #822), data indicating the message "304 Not Modified", that is, the response data 7L, is transmitted to the browsing terminal device 3A (#824). If the HTML file 7C is not stored, the HTML file 7C is immediately regenerated by the static page update process (see #806 in FIG. 13), and this is transmitted to the browsing terminal device 3A (#826). That is, dynamic delivery is performed.
[0102] 16 in response to an event that has occurred while the service is continuing. The web server 2 also performs the same processing for static pages 5 other than the static page 51.
[0103] According to this embodiment, the web server 2 basically provides the HTML file 7C of the static page 5 by static delivery. Also, when there is a possibility that the configuration of the static page 5 may change, such as when an article page 6 is added, updated, or deleted, the HTML file 7C of the static page 5 is temporarily deleted. Then, if there is a request for the static page 5 by the waiting time T, the HTML file 7C is regenerated and provided. In other words, the HTML file 7C is provided by dynamic delivery. On the other hand, if there is no request for the static page 5 by the waiting time T, the HTML file 7C is regenerated in preparation for static delivery. This delivery method allows the static page 5 to be delivered in a new state more stably than before without incurring too much cost.
[0104] Furthermore, while the web server 2 is waiting for the regeneration of a static page 5, if an article page 6 that shares a category name with the static page 5 is updated, deleted, or newly generated, the web server 2 extends the waiting period by resetting the scheduled regeneration time. This makes it possible to reduce the overall number of times the HTML file 7C is generated, and to achieve further stabilization.
[0105] 5. Modifications In this embodiment, when an article page 6 is added, updated, or deleted, the web server 2 registers the task data 7J of the static page 5 associated with the category name of the article page 6 in the task storage unit 246 (see FIG. 14) and deletes the HTML file 7C of the static page 5 from the static page file storage unit 242, but similar processing may be performed when other events occur. When a static portion of the static 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 static page 5 may be registered and the HTML file 7C of the static page 5 may be deleted.
[0106] As described above, the hash value of the HTML file 7C of the static page 5 may match before and after regeneration. In other words, the configuration of the static page 5 may not change substantially even if it is regenerated. Therefore, the web server 2 may determine whether the regeneration will change the configuration of the static page 5 before registering the response data 7L and deleting the HTML file 7C. Then, only if the configuration changes, the response data 7L may be registered and the HTML file 7C may be deleted. Note that whether the configuration changes may be determined by whether the members of the article list (for example, article list 50d of static page 50 shown in FIG. 5) change.
[0107] In this embodiment, the web server 2 regenerates the HTML file 7C when the scheduled regeneration time indicated in the task data 7J arrives, but if there is a surplus of resources (for example, if the usage rate of the main processor 21a is less than a predetermined value), the HTML file 7C may be regenerated without waiting for the scheduled regeneration time to arrive. If there are multiple pieces of task data 7J, the data with the earliest scheduled regeneration time may be given priority for regeneration.
[0108] In this embodiment, the regeneration and provision of the HTML file 7C of the static page 5 having a list of articles in the article page 6 is taken as an example, but the present invention can also be applied to the regeneration and provision of HTML files of other static pages (web pages). For example, the present invention can also be applied to the regeneration and provision of a web page having a timeline and broadcasting sports in real time.
[0109] In this embodiment, the means shown in FIG. 3 are provided collectively in the web server 2, but they may be provided distributed across a number of devices.
[0110] Additionally, the configuration of the entire or each part of the web page providing system 1 and the web server 2, the content of the processing, the order of processing, the data configuration, and the like may be modified as appropriate in accordance with the spirit of the present invention. [Explanation of symbols]
[0111] 2. Web Server 202 Web page file generation unit (generation means, management means) 205 Task Management Unit (Deletion Method) 206 Request response unit (transmission means) 5. Static Pages (Web Pages) 6 Article Pages 242 Fixed page file storage 243 Fixed page attribute storage unit (attribute storage means) 3A Viewer terminal device (client) 7C HTML File
Claims
1. A web page providing system for providing a web page, comprising: a web page storage means for storing web page data for displaying the web page; a generating means for regenerating the web page data stored in the web page storage means after a second event occurs when a first event occurs that may affect or does affect a configuration of the web page; a transmitting means for transmitting the web page data to the client when requested by the client; A web page providing system comprising:
2. a deletion means for deleting the web page data from the web page storage means when the first event occurs; having the second event being the request from the client when the web page data is not stored in the web page storage means, or the lapse of a predetermined time since the first event last occurred; The web page providing system according to claim 1 .
3. The predetermined time is set to be shorter as the frequency of access to the web page increases. The web page providing system according to claim 2 .
4. an attribute storage means for storing the generation date and time of the web page data; a management means for updating the generation date and time stored in the attribute storage means to the date and time when the web page data is regenerated by the generation means, if the contents of the whole or a predetermined part of the web page data before and after the regeneration are different, and not updating the generation date and time if they are the same; having the transmitting means transmits the web page data if the cache date and time of the web page presented by the client at the time of the request is older than the generation date and time stored in the attribute storage means, and transmits a message indicating that the web page has not been updated instead of the web page data if the cache date and time is newer.
4. The web page providing system according to claim 1.
5. The web page is a static page having a list of one or more article pages, The first event is an event in which an article page associated with a common category name with the web page is updated, deleted, or newly added.
4. The web page providing system according to claim 1.
6. A method for providing a web page, comprising the steps of: storing web page data for displaying the web page in a web page storage means; regenerating the web page data stored in the web page storage means after a second event occurs when a first event occurs that may affect or does affect a configuration of the web page; When requested by a client, the web page data is transmitted to the client. A method for providing a web page comprising the steps of:
7. 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, comprising: The computer includes: executing a process of regenerating the web page data stored in the web page storage means after a second event occurs when a first event occurs that may affect or will affect a configuration of the web page; When a request is received from a client, a process of transmitting the web page data to the client is executed. A computer program comprising:
