JP4671402B2 - Web page providing apparatus and web page providing method - Google Patents

Description

  The present invention relates to a web page providing apparatus and a web page providing method.

  In a network system known as the so-called Internet, various web pages (WWW documents) are provided from a WWW server to each WWW client using a mechanism called WWW (World Wide Web).

  A web page can be configured by mixing a plurality of types of content such as text, images, or audio. For the purpose of improving operability or visibility, a screen division technique called a frame may be used (Patent Document 1).

In the frame technique, for example, the screen can be divided into upper and lower sides or left and right, and different contents can be displayed in the divided display areas. However, in the frame technology, for example, it is not possible to bookmark in the middle of the screen transition, a request for the number of frames occurs in one request, the address information displayed on the web browser matches the actual display screen Such as lack of security reliability.
Therefore, for example, as known as Apache Struts Framework (Struts) and Tiles, a layout technology that provides similar functions without using a frame technology is also used.
JP 2004-246663 A

  The above new layout technology can provide the same function while eliminating the disadvantages of the conventional frame technology, but cannot cache only part of the screen provided to the web browser. If the frame technology is used, a part of the screen can be cached. However, as described above, since the frame technology has many disadvantages, it is not suitable for use in a web application.

  It is possible to provide an intermediate server called a proxy server between the WWW client and the WWW server, and to cache the entire screen on the intermediate server. However, in this case, the entire screen is simply cached, and cannot be cached for each part constituting the screen.

  Accordingly, an object of the present invention is to provide a web page providing apparatus and a web page providing method that can partially store and reuse a screen provided as a single web page. is there. Further objects of the present invention will become clear from the description of the embodiments described later.

  In order to solve the above-described problem, a web page providing apparatus according to one aspect of the present invention includes a plurality of web page generation units that respectively generate web pages including at least one content data, and each of these web page generation units. Storage control means for storing all or part of each generated web page in a storage means based on preset storage conditions, and predetermined layout information for each web page generated by each web page generation means And a layout control unit that generates a single web page and provides it to the web browser, and a request control unit that detects a request to the single web page from the web browser. When the request control unit detects a request from the web browser, the layout control unit generates a single web page by reusing at least a part of each web page stored in the storage unit. It is possible.

Examples of content data include text data, still image data, moving image data, audio data, music data, and the like. The web page can be generated using, for example, HTML (HyperText Markup Language), XML (eXtensible Markup Language), JSP (Java Server Pages), ASP (Active Server Pages), or the like. For example, in JSP and ASP, a program described in a web page can be executed on a WWW server and the processing result can be displayed, and a dynamic web page can be configured. Thus, web pages can be broadly classified into static web pages whose contents are fixed and dynamic web pages whose contents can change each time.
Examples of the storage means include rewritable storage devices such as a semiconductor memory and a hard disk drive. The storage control means stores all or part of the web page in the storage means in accordance with preset storage conditions.

When the request control means detects a request from the web browser, the layout control means obtains predetermined web pages. The layout control means arranges each web page at a predetermined position based on predetermined layout information and collects the web pages into a single web page.
In other words, this single web page is configured by combining a plurality of web pages into one page, and is handled as one web page, and is a frame technology that displays different web pages in each frame. Is different.

  The layout control unit can generate a single web page by reusing at least a part of the web page stored in the storage unit. As a result, the processing load can be reduced and the responsiveness to the web browser can be improved compared to the case of newly generating each web page that is a component of a single web page (completed web page). can do.

  When the request is detected by the request control means, the layout control means acquires a reusable web page from the storage means among the web pages stored in the storage means, and other than this reusable web page Each web page is newly generated by each web page generating means. Thereby, the web page generation means can be operated to the minimum necessary, the processing load of the web page providing apparatus can be reduced, and the responsiveness to the web browser can be improved.

  The storage control unit can control whether or not the storage unit stores each web page. Alternatively, the storage control unit can control whether or not each storage unit stores each web page based on the attribute of each web page.

  For example, the storage control unit can cause the storage unit to store a dynamic web page generated for each content of the request from the web browser. That is, by storing a dynamic web page in the storage unit, it is not necessary to operate the web page generation unit again, and a single web page can be generated efficiently and quickly.

  The storage control means may be divided into a shared web page shared by a plurality of users and an individual web page used individually by each user and stored in the storage means. For example, a web page commonly used for a plurality of users is temporarily stored as a common web page. On the other hand, web pages having different contents for each user are temporarily stored as individual web pages. Thereby, since the range which can be temporarily stored increases, it is possible to further reduce the load on the web page providing apparatus and improve the responsiveness.

  The storage control means can also store each web page in the storage means at a different timing for each web page. Examples of different timings include a case where a web page is stored every predetermined time set in advance, and a case where a web page is stored when a request from a web browser is generated. In this manner, each part (individual web page) constituting a single web page can be stored in the storage means at a different appropriate timing.

  A method for providing a web page according to another aspect of the present invention includes a step of detecting a request from a web browser, and a step of identifying a necessary web page based on predetermined layout information when a request is detected. A step of confirming whether there is a web page stored in the storage means among the specified web pages, a step of acquiring a web page stored in the storage means, and a step of A step of generating a web page that is not stored in the storage means, and arranging the generated web page and the web page acquired from the storage means on the basis of predetermined layout information, thereby providing a single web page. And the generated single web page to the web browser Including a step of faith, the.

  Further, after the step of generating a web page that is not stored in the storage unit, a step of storing the generated web page in the storage unit may be provided.

  All or some of the functions, means, and steps of the present invention may be configured as, for example, a computer program executed by a microcomputer. The computer program can be fixed and distributed on a storage medium such as a hard disk, an optical disk, or a semiconductor memory. Alternatively, the computer program can be distributed via a communication network such as the Internet.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. The web page providing apparatus (10) of the present embodiment includes a plurality of web page generating means (31) that respectively generate web pages (110, 120) including at least one content data, and each of these web page generating means (31 The storage control means (23) for storing all or a part of each web page (110, 120) generated by) in the storage means (11, 12) based on preset storage conditions, and each web page generation A single web page (200) is generated and provided to the web browser (2) by arranging each web page (110, 120) generated by the means (31) based on predetermined layout information (100). Layout control means (22) for performing the request, and request control means (21) for detecting a request from the web browser (2) to the single web page (200).
When the request control means (21) detects a request from the web browser (2), the layout control means (22) detects each web page (110, 120) stored in the storage means (11, 12). Reuse at least a portion of to generate a single web page (200).

  FIG. 1 is a block diagram showing the overall configuration of the web page providing apparatus 10. The web page providing apparatus 10 can be constructed as an information distribution computer such as a server, for example. The apparatus 10 is connected to the client terminal 1 so as to be capable of bidirectional communication via a communication network such as the Internet. In FIG. 1, only one client terminal 1 is shown, but in reality, a plurality of client terminals 1 can be connected.

  The apparatus 10 can be configured in a three-layer structure, for example, from a web server 20, an application server 30, and a database (“DB” in the figure) server 40. Each of these servers 20, 30, and 40 can be provided in a single computer, or can be provided separately in a plurality of computers. Each of these servers 20, 30, and 40 includes a hardware resource such as a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a hard disk drive, an input / output interface, and an OS (Operating System). ) And software resources such as device drivers can be used as appropriate.

  The web server 20 is an information processing unit that exchanges data with the web browser 2 operating on the client terminal 1. The web server 20 can include, for example, a request control unit 21, a layout control unit 22, and a cache control unit 23. For example, the request control unit 21 detects an HTTP (Hypertext Transfer Protocol) request from the web browser 2 and generates a response to the request. More specifically, when the request control unit 21 detects a request from the web browser 2 for a single web page generated by the layout control unit 22, the request control unit 21 internally generates a plurality of requests.

  The layout control unit 22 groups a plurality of web pages into a single web page based on the tile definition file F1 and the layout definition file F2. This single web page is the final display form provided to the web browser 2. That is, the single web page generated by the layout control unit 22 is derived from a plurality of web pages, but is finally configured as a single web page and handled as one web page. It is different from the screen. Hereinafter, a single web page may be referred to as a completed page, and each web page serving as the component may be referred to as a component page. In addition, the layout control unit 22 uses the cache definition file to reuse a component page that has already been generated and cached to generate a completed page.

  The cache control unit 23 manages data to be stored in the cache memory. As will be described later, the cache control unit 23 can use a memory such as a RAM, a hard disk drive, or the like as a cache device. The cache control unit 23 controls the cache for each partial page constituting the completed page based on the cache definition file F3 and the cache control definition file F4.

  The application server 30 operates a plurality of business logics 31 individually. The business logic 31 is, for example, a web application program for returning a search result or creating a page corresponding to input data.

  The DB server 40 is for controlling the database 41. The DB server 40 searches the database 41 in response to a request from the application server 30 and returns the result.

  FIG. 2 is an explanatory diagram showing the overall operation of the apparatus 10. For convenience of explanation, a case where the completed page 200 includes a “menu” component page 110, a “body” component page 120, and a “message” component page 130 will be described as an example. For this reason, the business logic 31 is shown separately in business logic 31 A for generating the “body” component page 120 and business logic 31 B for generating the “menu” component page 110.

  The web browser 2 accesses the web server 20 and transmits a request for updating the screen, for example (S1). When the request control unit 21 detects a request from the web browser 2, the request control unit 21 instructs the business logic 31A to generate the “body” component page 120 (S2). The business logic 31A generates and outputs a “body” parts page 120 (S3). Here, since the “body” parts page 120 is not cached, the business logic 31A is instructed to generate it immediately.

  Further, when the request control unit 21 receives a request from the web browser 2, the request control unit 21 notifies the layout control unit 22 of this request and instructs execution of the tile definition (S4). The layout control unit 22 reads the tile definition file F1 and selects the layout information 100 for generating the completed page 200.

  The layout information 100 includes information on where to place the component pages 110, 120, and 130. For example, in the layout information 100, an area 101 for arranging the component page 110, an area 102 for arranging the component page 120, and an area 103 for arranging the component page 130 are set. Specifically, for example, the tile definition file F1 and the layout definition file F2 correspond to the layout information 100.

  The layout control unit 22 refers to the layout information 100 to detect the component pages 110 to 130 necessary for generating the completed page 200, and starts acquiring the component pages 110 to 130. When the “body” component page 120 is output from the business logic 31A, the layout control unit 22 acquires the component page 120 (S5).

  On the other hand, when acquiring the “menu” component page 110, the layout control unit 22 first checks the cache control unit 23 for the presence of cache data (S6). The layout control unit 22 can specify the component data to be cached by referring to the cache definition file F3.

  When the cache control unit 23 receives an inquiry from the layout control unit 22, the cache control unit 23 refers to the cache definition file F 3 and confirms whether the “menu” component page 110 is cached. When the “menu” component page 110 is cached, the layout control unit 22 acquires the cached component page 110 (S10). Accordingly, the business logic 31B does not need to generate the component page 110, and the layout control unit 22 can immediately acquire the component page 110.

  For example, the cache data is deleted regularly or irregularly according to a cache management algorithm such as LRU (Least Recently Used). Therefore, the “menu” component page 110 to be cached may not be cached. In this case, the business logic 31B is instructed to generate the “menu” component page 110 (S7), and the business logic 31B newly generates and outputs the component page 110 (S8). The cache control unit 23 caches the newly generated component page 110 (S9).

  On the other hand, the layout control unit 22 acquires a static component page 130 such as a fixed text via a static file acquisition system (not shown) (S11).

  In this way, the layout control unit 22 acquires all necessary component pages 110 to 130, respectively. In accordance with the layout information 100, the component pages 110 to 130 are respectively arranged at predetermined positions, and an output screen (completed page 200) is generated (S12).

  Then, the generated completed page 200 is transmitted from the web server 20 to the web browser 2 via the communication network (S13). The web browser 2 displays a completed page 200 configured as a single web page. As described above, the completed page 200 is derived from the plurality of component pages 110 to 130 and includes a plurality of types of content data. Therefore, it looks similar to a frame screen without the frame, but unlike the frame screen, it is not composed of a plurality of web pages.

  Next, an example of each of the files F1 to F4 will be described. FIG. 3 is an explanatory diagram showing the tile definition file F1. The outline of the tile definition file F1 will be partially described. The tile definition file F1 specifies the layout definition file F2 whose layout is to be determined (F11). In addition, the title of the completed page 200 is specified in the tile definition file F1 (F12).

  Furthermore, in the tile definition file F1, a URL (Uniform Resource Locator) for generating and displaying a dynamic component page can be specified (F13). When specified as a dynamic component page, an internal request is issued to the business logic 31 that generates the component page. The tile definition file F1 also includes designation for displaying a static component page (F14).

  FIG. 4 is an explanatory diagram of the layout definition file F2. In the layout definition file F2, for example, a content name to be displayed is designated (F21). In the layout definition file F2, a content display position and the like can be designated.

  FIG. It is explanatory drawing which shows the cache definition file F3. In the cache definition file F3, at least one part page to be cached can be specified. Then, a cache control parameter can be set for each component page designated as a cache target.

  For example, whether the part page to be cached is shared by multiple users (cache type = “global”), or is it used only for individual users (cache type = “session”) Can be specified (F31). In the cache definition file F3, a plurality of parameters as keys for specifying cache data can be set (F32). Further, a cache control definition file F4 for controlling the cache memory can be designated (F33).

FIG. 6 is an explanatory diagram showing the cache control definition file F4. In the cache control definition file F4, for example, the type of the cache control system is designated (F41). As the cache control system, for example, (1) the cache is held in the memory, (2) the cache is held as a file on the hard disk, and (3) the cache is held in the memory. In this case, a method of using a storage device to be cached, such as holding as a file, can be mentioned.
In addition to this, for example, (4) If the cache is held as a file and the cache file size exceeds a certain amount, the cache area can be released, such as deleting from the oldest one. it can.

  Further, more detailed settings can be made in the cache control definition file F4 (F42). The setting items include, for example, (1) the name of the directory where the cache file is stored, (2) the maximum storage amount of the cache file stored in the hard disk, (3) the maximum storage amount of the cache stored in the memory, and (4) the web server. Whether or not to delete the cache when 20 is restarted.

  Next, the outline of the operation has already been described with reference to FIG. 2, but the outline of the screen output processing by the apparatus 10 will be described with reference to FIG. When detecting the request from the client terminal 1 (S21: YES), the web server 20 selects a layout (tile definition file F1 and layout definition file F2) (S22).

  The web server 20 refers to the cache definition file F3 and determines whether or not a cache-target component page is included in the selected layout (S23). When the component page designated as the cache target is used in the layout (S23: YES), the web server 20 determines whether or not the component page is cached (S24). When the component page is cached (S24: YES), the web server 20 reads and acquires the cached component page from the memory or the like (S25).

On the other hand, when the part page to be cached is not used in the selected layout (S23: NO), the web server 20 determines whether or not a part page needs to be newly generated (S26). ). If it is determined that generation is necessary (S26: YES), the web server 20 causes the business logic 31 to generate a component page (S27).
The web server 20 determines whether or not to cache the generated component page based on the cache definition file F3 (S28). When the generated component page is cached (S28: YES), the web server 20 stores the component page in a predetermined storage device (S29) and then acquires the component page to generate a completed page. (S30).

  On the other hand, when the component page to be cached is not cached (S24: NO), that is, when a cache miss occurs, the web server 20 issues an instruction to the business logic 31 to newly generate the component page. (S27). Then, the web server 20 caches the generated component page (S28: YES, S29) and uses it to create a completed page (S30).

  The web server 20 determines whether or not all the component pages necessary for creating the completed page have been acquired (S31). When there is a component page that has not been acquired (S31: NO), the web server 20 repeats the above-described processing (S23 to S30).

  When all necessary component pages have been acquired (S31: YES), the web server 20 creates a completed page (S32) and transmits it to the client terminal 1 (S33).

  FIG. 8 is a flowchart showing an outline of a process for generating a cache. When the web server 20 acquires the component data generated by the business logic 31 (S41), the web server 20 refers to the cache definition file F3 (S42) and determines whether or not this component page is designated as a cache target (S43). ). If not cacheable, this process ends (S43: NO).

  When the component page designated as the cache target is acquired (S43: YES), the web server 20 determines whether or not the component page is designated to be shared (S44). The sharing specification indicates a parts page that is commonly used by a plurality of users. In the case of a component page designated for sharing (S44: YES), the web server 20 stores it as a shared cache (S45), and updates the cache management table T2 (S46). The cache management table T2 will be described later.

  When a component page that is not designated for sharing is acquired (S44: NO), that is, in the case of a component page that is used for each user, the web server 20 identifies to which user the component page is applied. To obtain the information (S47). In this embodiment, session identification information (“session ID” in the figure) for identifying a session with the client terminal 1 is used as the user specifying information. The web server 20 associates the acquired component page with the session identification information, stores them in a predetermined storage device (S48), and updates the cache management table T2 (S49).

  FIG. 9 is an explanatory diagram showing an example in which the caching method is different depending on the attribute of each component page. As described above, in the cache definition file F3, a component page to be cached can be designated, and a cache type (“shared attribute” in FIG. 9) and the like can be set for each designated component page.

  The component page can be classified into, for example, a dynamic component page and a static component page. The dynamic part page is generated, for example, every time it is requested, and its contents are different every time. The static part page is, for example, a page whose contents are constant and do not change.

  In this embodiment, both the dynamic component page and the static component page can be cached. However, if the dynamic component page is cached, it is not necessary to execute the business logic 31 and the server load is reduced. The Therefore, for example, the cache definition file F3 and the cache control definition file F4 may be configured to cache the dynamic part page preferentially. For example, the dynamic part page is preferentially stored in the memory, and when the free space of the memory becomes small, the static part page is deleted first. Alternatively, the dynamic part page can be acquired more quickly by holding the dynamic part page in the memory and the static part page in the hard disk, and the responsiveness of the web server 20 can be further improved. it can.

  FIG. 10 is an explanatory diagram showing the cache management table T2 and the like. The cache management table T2 includes, for example, page identification information (“PID” in the figure), a shared attribute of each component page, a session ID, a device name in which the component page is stored, and a storage destination address of the component page. The component page update triggers can be associated with each other.

  The page identification information is information for identifying each cached component page, and is generated, for example, by combining a plurality of parameter values. Even for the same page name, the value of the page identification information varies depending on the display content, the update time, and the like. As described above, the sharing attribute is information for distinguishing whether the component page is a page shared by a plurality of users or a page used individually by each user. The session ID is information for identifying which user is used when the component page is used for each user. The storage destination device name is information for specifying the device in which the component page is stored.

  The update trigger is information for designating the timing for caching the component page. Examples of the update trigger include (1) every predetermined time, (2) every time an update of the component page is requested, and the like. That is, for example, the cache can be updated regularly or irregularly according to characteristics such as display contents of the component page. For example, in the case of a component page that displays a satellite image, the cache can be updated in accordance with the update time of the business logic 31 that outputs the satellite image. Further, for example, in the case of a component page that displays a search result, the cache can be updated when a search is requested by the user.

  In the lower part of FIG. 10, a plurality of types of storage devices for caching component data are shown. Here, for example, one storage device is the memory 11, and the other storage device is the hard disk 12.

  Both the memory 11 and the hard disk 12 are randomly accessible storage devices, but the memory 11 can be accessed faster than the hard disk 12 from the viewpoint of accessibility from the CPU. On the other hand, in terms of storage capacity, the hard disk 12 can store more component pages than the memory 11.

  Therefore, for example, based on the characteristics of such a storage device, a component page that requires quicker access or a component page that is frequently accessed is stored in the memory 11, and other component pages are stored in the hard disk 12. be able to. Further, for example, the access frequency is monitored, and a component page whose access frequency has reached a predetermined value or more is transferred from the hard disk 12 to the memory 11. Conversely, a component page whose access frequency has reached the predetermined value or less is transferred from the memory 11 to the hard disk 12. It can also be moved to. Alternatively, the storage devices 11 and 12 may be moved based on the elapsed time since the last use, instead of the access frequency.

  Since this embodiment is configured as described above, the following effects can be obtained. In this embodiment, each component page constituting the completed page can be individually cached, and the completed page can be generated by reusing the cached component page. Therefore, it is not necessary to newly generate all the component pages each time a request is made from the client terminal 1, and the processing load on the web server 20 and the application server 30 can be reduced. Performance can be improved.

  In this embodiment, the shared attribute can be designated for each component page. Therefore, the range of parts pages that can be cached can be expanded, thereby further reducing the processing load and improving the responsiveness. In other words, in this embodiment, even if a component page includes user-specific information, the user-specific component page is cached by managing it in association with information (session ID) for specifying the user. And adopt a configuration that can be reused. Therefore, the number of parts pages that can be cached is increased, and the possibility of reuse is increased, thereby further reducing the server load and improving the responsiveness.

  In the present embodiment, a dynamic component page generated for each content of a request from the web browser 2 can be cached. Therefore, there is no need to run the business logic 31 to recreate the component page, and the server load can be further reduced and the responsiveness can be improved.

  In this embodiment, a configuration is adopted in which caching is possible at different timings for each component page. Therefore, each component page can be cached at an appropriate timing according to the feature of each component page.

  A second embodiment will be described with reference to FIG. In this embodiment, it is monitored whether or not it is time to update the cache of each component page, and the cache data is automatically updated.

  FIG. 11 is a flowchart showing an outline of the cache generation processing of this embodiment. The web server 20 refers to the cache definition file F3 (S51), and determines whether or not the cache data update time has come (S52).

  When it is time to update the component page cached in the memory or the like (S52: YES), the web server 20 acquires the latest data of the component page (S53). For example, if the component page is a dynamic page, an internal instruction is issued to the business logic 31 that generates the component page to generate a new component page.

  When acquiring the latest component page, the web server 20 stores the component page in a memory or the like (S54), and updates the cache management table T2 (S55). The web server 20 determines whether or not the cache update has been performed for all the component pages registered in the cache definition file F3 (S56). If the cache update time for the component page has not arrived (S52: NO), S53 to S55 are skipped, and the process proceeds to S56.

  When there is a part page that has not been determined to be updated (S56: NO), the web server 20 moves to the next part page registered in the cache definition file F3 (S57), and the above-described S51 to S51. S56 is repeated respectively. Then, when the web server 20 determines whether or not there is a cache update for all the component pages and updates the cache data of the component data that needs to be updated (S56: YES), this process ends.

  This embodiment, which is configured in this way, also has the same effect as the above embodiment. In addition, in this embodiment, whether or not to update the cache data of the parts page is determined regularly (or irregularly) regardless of whether there is a request from the client, and the cache is automatically stored. The configuration is updated. Therefore, in this embodiment, for example, the cache data can be kept up-to-date before receiving a request from the client, and a response to the request can be made promptly.

  As a modification of the present embodiment, the processing load of the web server 20 is monitored, and when the processing load is equal to or less than a predetermined value, that is, the cache data is automatically used by using a time zone when the load of the web server 20 is light. Can also be updated. In addition, for example, considering the attributes of each component page (whether it is a shared page or not, the frequency of access, etc.), the component pages with relatively high necessity regularly update the cache, Low parts pages can also wait for requests from clients to update the cache.

  The present invention is not limited to the above-described embodiment. A person skilled in the art can make various additions and changes within the scope of the present invention. For example, those skilled in the art can appropriately combine the above embodiments.

It is a block diagram which shows the whole structure of the web page provision apparatus by a present Example. It is composition explanatory drawing which shows the whole operation | movement etc. of a web page provision apparatus. It is explanatory drawing which shows an example of a type definition file. It is explanatory drawing which shows an example of a layout definition file. It is explanatory drawing which shows an example of a cache definition file. It is explanatory drawing which shows an example of a cache control definition file. It is a flowchart which shows the process which provides the completed page to a client. It is a flowchart which shows a cache production | generation process. It is explanatory drawing which shows the relationship between a cache definition file and the kind of cache object. It is explanatory drawing which shows the relationship between the storage device used for a cache management table and a cache. It is a flowchart which shows the cache production | generation process by the other Example of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Client terminal, 2 ... Web browser, 10 ... Web page provision apparatus, 11 ... Memory, 12 ... Hard disk, 20 ... Web server, 21 ... Request control part, 22 ... Layout control part, 23 ... Cache control part, 30 ... Application server 31, 31A, 31B ... business logic, 40 ... database server, 100 ... layout information, 101, 102, 103 ... parts page display area, 110, 120, 130 ... parts page, 200 ... completed page, F1 ... Tile definition file, F2 ... layout definition file, F3 ... cache definition file, F4 ... cache control definition file, T2 ... cache management table

Claims (7)

A plurality of web page generation means for generating web pages each including at least one content data;
All or part of each web page generated by each web page generation means is divided into a shared web page shared by a plurality of users and an individual web page used individually by each user, and cached. a storage control means for storing in a memory,
When storing the individual web page in the cache memory , the session identification information for indicating to which user of the plurality of users the individual web page is associated with the individual web page in association with each other. Stored in cache memory , and
Each shared web page includes both a dynamic web page generated as a result of the execution of business logic included in each web page, and a static web page whose content does not change. wherein the individual webs are divided into a page can be stored in the cache memory, further, said dynamic web pages give priority to the static web pages Ru is the storage memory control means and,
Layout control means for generating a single web page and providing it to a web browser by arranging each web page generated by each web page generation means based on predetermined layout information; and
Request control means for detecting a request from the web browser to the single web page,
The layout control means, when a request from the web browser is detected by the request control means, reuses at least a part of each web page stored in the cache memory , and A web page providing apparatus capable of generating a web page. When the request is detected by the request control unit, the layout control unit acquires a reusable web page from the cache memory among the web pages stored in the cache memory , The web page providing apparatus according to claim 1, wherein each web page other than a usable web page is newly generated by each web page generating unit. The web page providing apparatus according to claim 1 , wherein the storage control unit stores a dynamic web page generated for each content of a request from the web browser in the cache memory . 2. The web page providing apparatus according to claim 1, wherein the storage control unit is capable of storing each web page in the cache memory at a predetermined time or at a timing when an update is requested. The cache memory includes one cache memory and the other cache memory , and the one cache memory is accessible at a higher speed than the other cache memory ,
The storage control unit stores a web page having a relatively high access frequency among the web pages in the one cache memory , and a web page having a relatively low access frequency among the web pages is the other web page. The web page providing apparatus according to claim 1, wherein the apparatus is stored in a cache memory . Detecting a request from a web browser;
If the request is detected, identifying a required web page based on predetermined layout information;
Checking whether there is a web page stored in a cache memory among the identified web pages;
Obtaining a web page stored in the cache memory ;
Generating a web page that is not stored in the cache memory among the identified web pages;
Dividing the generated web page into a shared web page shared by a plurality of users and an individual web page used individually by each user, and storing the web page in a cache memory , When storing in the cache memory , session identification information for indicating to which of the plurality of users the individual web page is applied and the individual web page are associated with each other and stored in the cache memory to, and,
Each shared web page includes both a dynamic web page generated as a result of the execution of business logic included in each web page, and a static web page whose content does not change. the divided into the individual web pages can be stored in the cache memory, further comprising the steps of the dynamic web page Ru is the storage in preference to the static web pages and,
By arranging each based web pages retrieved from a web page and said cache memory said generated in the predetermined layout information, and generating a single web page,
Sending the generated single web page to the web browser;
Web page providing method including A first function for detecting a request from a web browser;
A plurality of second functions for generating web pages each including at least one content data;
A cache memory in which all or part of each web page generated by each of the second functions is divided into a shared web page shared by a plurality of users and an individual web page used individually by each user. Session identification information for indicating to which user of the plurality of users the individual web page is applied when the individual web page is stored in the cache memory. And the individual web page in association with each other and stored in the cache memory , and
Each shared web page includes both a dynamic web page generated as a result of the execution of business logic included in each web page, and a static web page whose content does not change. wherein the individual webs are divided into a page can be stored in the cache memory, further, a third function of said dynamic web pages give priority to the static web pages Ru is the storage and,
When the request is detected, a web page stored in the cache memory and a web page newly generated by the second function are arranged based on predetermined layout information, respectively. A fourth function for generating a web page of
A fifth function for transmitting the generated single web page to the web browser;
A computer program for realizing each on a computer.

Images