JPH11175447A - Data repeater system and computer readable record medium for recording data relay program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To hold only necessary data in relayed data as history information. SOLUTION: A request analyzing means 23 receives a request for obtaining data from a data using means 11, and analyzes whether or not a request for obtaining data is a request for relaying data or a request for obtaining history information. When the request for obtaining data is a request for relaying data, the request analyzing means 23 extracts the name of data from the request for obtaining data. When the request for obtaining data is the request for relaying data, a data requesting means 24 receives data pertinent to the name of the data extracted by the request analyzing means 23 from a data supplying means 12. When the request for obtaining data is the request for relaying data, and a processing to be operated according to the request for obtaining data is not suitable to a history unnecessity condition 22, a history managing means 25 stores the data received by a data requesting means, the name of the data, and the time information of a time when the data relay processing is operated as history information in a history information holding means 21 by making them correspond to each other. An outputting means 26 outputs data to the data using means.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a data relay apparatus and a computer-readable recording medium storing a data relay program, and more particularly to a data relay apparatus for holding relayed data as history information and a computer having such a data relay apparatus. The present invention relates to a computer-readable recording medium on which a data relay program for performing the program is recorded.

[0002]

2. Description of the Related Art In recent years, on the Internet, WWW (W
The transmission and reception of information using the Old Wide Web is becoming popular. With WWW, users can easily access information around the world.

A user browses page data on a WWW server using client software called a browser (hereinafter, simply referred to as “client”).
In order to access information on the WWW, an identifier called a URL (Uniform Resource Locator) indicating the position of data is input to a browser. Then, a request for the URL is transmitted from the browser to the WWW server,
Data corresponding to the URL is returned. Then, the data is displayed on the browser, and the user can browse the contents of the data.

[0004] In this way, the user browses the data on the WWW, but since the information on the WWW is constantly changing, the same contents cannot always be browsed at the same URL. For example, on newspaper homepages, the content of data is updated several times a day in most cases. Therefore, in order to re-view the viewed data later, the user has to save the page in some way. For example, if you store information about your favorite data in the computer where the client is running,
Even if the content of the data in the WWW server has been updated, the data before the update can be browsed.

[0005]

However, when data browsed in the past is stored in each computer on which the client is running, the data cannot be accessed from a plurality of clients. If data browsed in the past is stored as history information and the history information can be accessed from a plurality of computers, the history information can be shared between members of the same group, which is very convenient. Therefore, it is conceivable to automatically store data to be relayed as history information in a device that relays data (a data relay device) such as a proxy server.

However, if all the relayed data is held in the data relay device, there is a possibility that unnecessary data may be held. If unnecessary data is kept stored, a large amount of useless information is accumulated in the storage device of the data relay device.

Therefore, it is necessary not to store unnecessary data. For example, in a banner advertisement on a WWW page, a client requests different data with the same name at regular intervals from a client, but in many cases, it is not necessary to retain data relating to the advertisement as history information.

The present invention has been made in view of the above points, and has as its object to provide a data relay device that retains only necessary data among relayed data as history information.

Another object of the present invention is to provide a computer-readable recording medium on which a data relay program for retaining only necessary data among relayed data as history information is recorded. I do.

[0010]

According to the present invention, in order to solve the above-mentioned problems, a data use means for utilizing data obtained by request and a data supply means for supplying retained data on demand. In a data relay device that relays data, a history holding unit that holds history information of relayed data, and a history unnecessary condition holding unit that stores a history unnecessary condition in which a condition for not holding history information is stored in the history holding unit. , Upon receiving a data acquisition request from the data usage means,
Analyzing whether the data acquisition request is a data relay request or a history information acquisition request, and extracting the data name from the data acquisition request when the data acquisition request is a data relay request, If the request is history information acquisition request, request analysis means for extracting data name and time information from the data acquisition request, and if the data acquisition request is a data relay request, the request analysis means Data requesting means for requesting data corresponding to the name of the extracted data from the data supply means and receiving data sent from the data supply means in response to the request, wherein the data acquisition request is a data relay request, and If the data acquisition request does not meet the history unnecessary condition, the data received by the data request unit, the name of the data, and the data relay process While the time information of the performed time is stored in the history holding unit as history information in association with the data, the data received by the data request unit is output data, and when the data acquisition request is a history information acquisition request, History management means for searching the history holding means for history information matching the name and time information of the data extracted by the request analysis means, and using data included in the detected history information as output data; and There is provided a data relay device comprising: output means for outputting the output data specified by the history management means to a data use means which is an output source of an acquisition request.

According to such a data relay device, when a data acquisition request for relaying data is output from the data utilization means, the data name is extracted from the data acquisition request by the request analysis means. Then, the data requesting means obtains data corresponding to the name of the data extracted by the request analyzing means from the data supplying means. The data obtained by the data request unit is passed to the history management unit. In the history management unit, it is determined whether or not the data relay process in response to the data acquisition request conforms to the history unnecessary condition held in the history unnecessary condition holding unit. Only when the result of the determination does not satisfy the history unnecessary condition, the history management means stores the time information indicating the time of the data relay processing, the name of the data, and the content of the data in the history holding means in association with each other. Then, the data is output by the output means to the data using means.

In a data relay apparatus for relaying data between a data use unit that uses data obtained by request and a data supply unit that supplies held data in response to a request, a history of the relayed data is provided. A history holding unit that holds information, and upon receiving a data acquisition request from the data using unit, analyzes whether the data acquisition request is a data relay request or a history information acquisition request, and determines whether the data acquisition request is a data relay request. In the case, a request analysis unit that extracts a data name from the data acquisition request, and extracts the data name and time information from the data acquisition request when the data acquisition request is a history information acquisition request. When a data acquisition request is received from the data using means, the data name, host name, and request processing time are associated with the data And log holding means for holding as broadcast,
When the data acquisition request is a data relay request, the request analysis unit requests data corresponding to the name of the data extracted from the data supply unit, and the data transmitted from the data supply unit in response to the request. Receiving data requesting means, the data acquisition request is a data relay request, and the presence or absence of data access periodicity is determined based on log information stored in the log holding means. When it is determined that there is no data, the data received by the data request unit, the name of the data, and the time information of the time at which the data relay process was performed are stored in the history holding unit as history information in association with each other, The data received by the data request unit is output data, and when the data acquisition request is a history information acquisition request, the request analysis unit extracts History information matching the detected data name and time information, from the history holding means, a history management means for outputting data included in the detected history information as output data, and an output source of the data acquisition request. An output means for outputting output data specified by the history management means to a certain data using means is provided.

According to such a data relay device, when a data acquisition request for relaying data is output from the data utilization means, the request analysis means extracts the data name from the data acquisition request and , Log information is held by log holding means. Then, the data requesting means obtains data corresponding to the name of the data extracted by the request analyzing means from the data supplying means. The data obtained by the data request unit is passed to the history management unit. In the history management unit, the periodicity of the data access is determined based on the log information stored in the log information storage unit. Only when it is determined that the data is not periodic, the history management unit stores the time information indicating the time of the data relay process, the name of the data, and the content of the data in the history holding unit in association with each other. Then, the data is output by the output means to the data using means.

According to another aspect of the present invention, there is provided a method for relaying data between a data use unit that uses data obtained by request and a data supply unit that supplies held data in response to a request. A history holding unit for holding history information of relayed data in a computer-readable recording medium on which a data relay program is recorded, and a history unnecessary condition for storing a history unnecessary condition in which a condition for not holding history information is stored in the history holding unit. Holding means, upon receiving a data acquisition request from the data utilization means, analyzes whether the data acquisition request is a data relay request or a history information acquisition request,
If the data acquisition request is a data relay request, the data name is extracted from the data acquisition request.If the data acquisition request is a history information acquisition request, the data name is extracted from the data acquisition request. Request analysis means for extracting the time information, when the data acquisition request is a data relay request, requests data corresponding to the name of the data extracted by the request analysis means to the data supply means; A data requesting unit for receiving data sent from the data supply unit, wherein the data requesting unit is a data relaying request, and the data obtaining request does not conform to the history unnecessary condition. And stores the received data, the name of the data, and the time information of the time at which the data relaying process was performed as history information in the history holding unit. At the same time, the data received by the data request unit is output data, and when the data acquisition request is a history information acquisition request, history information matching the data name and time information extracted by the request analysis unit is output. A history management unit that retrieves data from the history holding unit and uses data included in the detected history information as output data; and an output specified by the history management unit to a data use unit that is an output source of the data acquisition request. A computer-readable recording medium that records a data relay program, which causes a computer to function as an output unit that outputs data, is provided.

According to a computer-readable recording medium on which such a data relay program is recorded, by causing the computer to execute the recorded data relay program, the function of the data relay apparatus having the above-mentioned history unnecessary condition holding means is realized. Is implemented on a computer.

Further, a computer-readable recording medium for recording a data relay program for relaying data between a data use means for using data obtained by request and a data supply means for supplying held data in response to a request. In a possible recording medium, history holding means for holding the history information of the relayed data, upon receiving a data acquisition request from the data utilization means, analyzes whether the data acquisition request is a data relay request or a history information acquisition request, If the data acquisition request is a data relay request, the data name is extracted from the data acquisition request.If the data acquisition request is a history information acquisition request, the data name is extracted from the data acquisition request. Request analysis means for extracting time information, associating information included in the data acquisition request with time information indicating request processing time Log holding means for holding as log information, when the data acquisition request is a data relay request, requests data corresponding to the name of the data extracted by the request analysis means to the data supply means, and in response to the request, A data requesting unit for receiving data transmitted from the supplying unit, wherein the data acquisition request is a data relaying request, and determines whether or not data access is periodic based on log information stored in the log holding unit. If it is determined that the access is not the same type of periodic access, the data received by the data request unit, the name of the data, and the time information of the time at which the data relay process was performed are associated with each other, and While storing in the holding means, the data received by the data request means as output data,
When the data acquisition request is a history information acquisition request,
Searching the history information that matches the name and time information of the data extracted by the request analysis unit from the history holding unit,
A computer as a history management unit that outputs data included in the detected history information as output data, and an output unit that outputs the output data specified by the history management unit to a data use unit that is an output source of the data acquisition request; And a computer-readable recording medium on which a data relay program is recorded.

According to the computer-readable recording medium on which such a data relay program is recorded, by causing the computer to execute the recorded data relay program, the function of the data relay apparatus having the above-described log holding means is improved. Implemented on a computer.

[0018]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a diagram illustrating the principle of the present invention. The data relay device 20 of the present invention includes a data use unit 11 that uses data obtained by request,
This relays data with the data supply means 12 which supplies 2a on demand.

The data relay device 20 includes the following elements. The history holding unit 21 holds history information of relayed data. The history unnecessary condition holding unit 22 holds a history unnecessary condition in which a condition for not holding history information in the history holding unit 21 is defined.

The request analysis means 23 is a data
When a data acquisition request is received from the server, it analyzes whether the data acquisition request is a data relay request or a history information acquisition request. If the data acquisition request is a data relay request, extract the data name from the data acquisition request.If the data acquisition request is a history information acquisition request, extract the data name and time information from the data acquisition request. Extract.

When the data acquisition request is a data relaying request, the data requesting unit 24 sends data corresponding to the name of the data extracted by the request analyzing unit 23 to the data supplying unit 1.
2 and receives the data sent from the data supply means 12 in response to the request.

When the data acquisition request is a data relay request and the processing performed in response to the data acquisition request does not meet the history unnecessary condition 22, the history management unit 25 receives the data acquisition request. The data, the name of the data, and the time information of the time at which the data relay processing was performed are stored in the history holding unit 21 as history information in association with each other. At this time, the data received by the data request unit is used as output data. If the data acquisition request is a history information acquisition request, history information matching the data name and time information extracted by the request analysis unit 23 is stored in the history holding unit 21.
, And the data included in the detected history information is used as output data.

The output unit 26 outputs the output data specified by the history management unit 25 to the data use unit that is the output source of the data acquisition request. In such a configuration,
When a data acquisition request for relaying the data 12a is output from the data use unit 11, the request analysis unit 23 extracts a data name from the data acquisition request. Then, the data requesting unit 24 obtains the data 12 a corresponding to the name of the data extracted by the request analyzing unit 23 from the data supplying unit 12. The data 12a acquired by the data request unit 24 is passed to the history management unit 25. The history management unit 25 determines whether or not the data relay process in response to the data acquisition request matches the history unnecessary condition stored in the history unnecessary condition holding unit 22. Only when the determination result indicates that the history unnecessary condition is not satisfied, the history management unit 25 sets the time information indicating the time of the data relay
The name of the data 12a and the contents of the data 12a are stored in the history holding unit 21 in association with each other. And data 12
a is output to the data use unit 11 by the output unit 26.

As described above, when the history unnecessary condition is satisfied, the history information of the relayed data is not stored in the data relay device, so that a large amount of unnecessary data is stored in the history holding unit 21. Can be prevented.

Hereinafter, an embodiment of the present invention will be described in detail by taking as an example a case where the present invention is applied to a data relay device connected to the Internet. FIG. 2 is a block diagram illustrating a system configuration according to the first embodiment of this invention. This figure shows a client 4 that is a WWW browser.
1a and 42a show an example of browsing HTML documents stored in WWW servers 61 and 63 existing on the Internet 72 via a data relay device 50 according to the present invention.

In the figure, a plurality of hosts 41, 42
It is connected to the data relay device 50 via the network 71. The data relay device 50 is connected to the Internet 72
Are connected to a plurality of WWW servers 61 and 63. The WWW servers 61 and 63 each store data 6
2, 64 are held.

In each of the hosts 41 and 42, clients 41a and 42a as WWW browsers are executed.
The clients 41a and 42a make a request for data to the data relay device 50 and receive the requested data. The received data is displayed on the screen by the clients 41a and 42a.

The data relay device 50 is composed of the following elements. The request analysis unit 51 includes the hosts 41 and 4
2 is determined as to whether the data acquisition request is a data relay request or a history information acquisition request. If the data acquisition request is a data relay request, the data name is extracted from the data acquisition request. If the data acquisition request is a history information acquisition request, data name and time information are extracted from the data acquisition request.

The data request unit 52 receives the name of the data extracted by the request analysis unit 51 when the data acquisition request is a data relay request. When the name of the data is input, the name of the data is input to the name analysis unit 53.
The request analysis unit 51 requests the server corresponding to the identifier returned from the name analysis unit 53 for data corresponding to the name of the data extracted, and receives the data from the server.

The name analysis unit 53 analyzes the name of the data input from the data request unit 52 and returns a server identifier corresponding to the name. When the data acquisition request is a data relay request, the history management unit 54 compares the contents of the data acquisition request with the history unnecessary condition set in the history unnecessary condition holding unit 57, and determines whether the history information is to be held. Judge not. As a result of the comparison, if it is determined that the history unnecessary condition is not met, the data received by the data request unit 52 is associated with the history information by associating the data with the name of the data, the content of the data, and the time information indicating the time when the client sent the request. Is stored in the history holding unit 55. Then, the history management unit 54
The data received by the data request unit 52 is used as output data. When the data acquisition request is a history information acquisition request, the history management unit 54 matches the data name and the time information indicated by the data acquisition request from the data held in the history holding unit 55. History information is searched, and the search result is used as output data.

The history unnecessary condition holding section 57 holds history unnecessary conditions. As the history unnecessary condition, for example, a name of data that does not hold history information can be specified, or all data held in a certain server can be specified not to hold history information.

The history holding unit 55 holds the name of the data relayed by the data relay device 50, the content of the data, and the time at which the client sent the request as history information in association with each other.

The output unit 56 outputs the contents of the output data specified by the history management unit 54 to the clients 41a and 42a. The servers 61 and 63 hold and manage the contents of the data 62 and 64 by adding other information.

Here, the correspondence between the components in the embodiment of FIG. 2 and the components in the principle configuration of FIG. 1 will be described. 1 corresponds to the clients 41a and 42a in FIG. Data supply means 1 of FIG.
2 corresponds to the WWW servers 61 and 63 in FIG. FIG.
Each of the components in the data relay device 20 corresponds to each component in the data relay device 50 in FIG. The data request unit 24 corresponds to a function obtained by combining the data request unit 52 and the name analysis unit 53.

In the system having such a configuration, a processing procedure in the case where the data relay device does not hold data matching the name of data registered in advance as history information in response to a data acquisition request from a client will be described below. explain.

Here, it is assumed that the history unnecessary condition holding section 57 holds the following history unnecessary conditions. FIG. 3 is a diagram illustrating an example of the history unnecessary condition.

The first condition is that the data name is "url
If "1", no data is retained. That is.
The second condition is that "the name of the data is the keyword" banner "
Or, if a "banner" is included, no data is retained. That is.

The third condition is that "when the server holding data is" www.aaa.bbb ", no data is held. That is. The fourth condition is that if the data includes a sentence that includes both the keyword “download” and the keyword “prohibited”, the data is not retained. That is.

The fifth condition is that if the server holding the data belongs to the domain “.ddd.eee.co.jp”,
Do not retain data. That is. In a state where these five conditions are set as the history unnecessary conditions, the user transmits a data acquisition request from the client 41a to the data relay device 50 in order to browse the data corresponding to the data name “url1”. Consider the case. At this time, the data acquisition request transmitted by the client 41a is:
These are:

FIG. 4 is a diagram showing an example of a data acquisition request transmitted by a client. This data acquisition request 81
Is that the client 41a receives an HTTP (Hypertext Transfe
r Protocol) header information. This header information indicates that the data of “url1” is to be obtained by HTTP version 1.1.

Data acquisition request 8 from client 41a
When 1 is output, the request analysis unit 51 analyzes the contents of the data acquisition request 81, and determines whether the data acquisition request is a data relay request or a history information acquisition request. In this example, if time information is not specified in the data acquisition request, the data acquisition request is a data relay request. If time information is specified, the data acquisition request is a history information acquisition request. It is assumed that In the example of FIG. 4, since the time information is not specified, the request analysis unit 5
1, it is determined that the request is a data relay request, and the name “url1” of the data to be acquired is extracted. The extracted data name “url1” is sent to the data request unit 52 and the history management unit 54. The data request unit 52 inputs the name “url1” of the received data to the name analysis unit 53. Then, the name analysis unit 53 returns the IP address of the WWW server 61. The data request unit 52 sends the data 6 to the WWW server 61 based on the received IP address.
2 is sent.

The WWW server 61 receives the data acquisition request from the data relay device 50, and receives the data name "url".
The data 62 corresponding to "1" is returned to the data relay device 50. In the data relay device 50, the data request unit 52 receives the data 62 sent from the WWW server 61. The data request unit 52 transmits the received data 62 to the history management unit 5
Pass to 4.

In the history management unit 54, the data name “url 1” received from the request analysis unit 51 and the data request unit 5
It analyzes the contents of the data 62 received from 2 and determines whether or not it meets the history unnecessary condition. In this example, since the data name “url1” satisfies the first condition of the history unnecessary condition, the history management unit 54
Is not stored in the history holding unit 55, but is passed to the output unit 56. The output unit 56 transmits the received data 62 to the client 41
output to a.

Client 41 receiving data 62
In a, the content of the received data 62 is displayed on the screen of the display device. Although the above example is a case where the first condition of the history unnecessary condition is satisfied, the history information is not held in the data relay device 50 even when the following data acquisition request is output.

For example, if the client is "http: //www.dd
d.eee / banner.gif ", the data relay device requests the data corresponding to the URL because the URL includes the keyword" banner "and satisfies the second condition of the history unnecessary condition. Do not keep the data corresponding to the name.

Further, when the client receives “http: //www.aa
a.bbb / index.html ", the WWW server indicated by the URL requests" www.aaa.
bbb ", which satisfies the third condition of the history unnecessary condition, so that the data relay device does not hold data corresponding to this name.

If the data requested by the client includes the sentence "prohibit download", the data relay device satisfies the fourth condition of the history unnecessary condition. Do not keep.

When the data requested by the client is held by a server belonging to the domain ".ddd.eee.co.jp", the data relay device satisfies the fifth condition of the history unnecessary condition. Do not keep the data corresponding to the name.

The above example is a case where the history unnecessary condition is satisfied. If “url1” does not satisfy the history unnecessary condition of the history unnecessary condition holding unit 57, the history management unit 54 Time information T indicating the time at which data was relayed
11. The data name “url1” is associated with the content of the data 62 and stored in the history information holding unit 55. Then, the data 62 is output by the output unit 56. In addition,
In the first embodiment, the data relay device is configured to include the history unnecessary condition holding unit. However, a condition server that holds the history unnecessary condition may exist on the network.

In this case, the data relay device is newly provided with a condition server name holding unit. The condition server name holding unit holds the name of the condition server holding the history unnecessary condition. The condition server is connected to the data relay device via the Internet. The condition server holds the history unnecessary condition and responds to the inquiry about the history unnecessary condition from the data relay device.

The data relay apparatus periodically inquires of the condition server, acquires the history unnecessary condition, and stores it in the history unnecessary condition holding unit. As in the first embodiment, the data relay device refers to the history unnecessary condition stored in the history unnecessary condition holding unit and determines whether to store the data to be relayed in the history holding means.

With this configuration, it becomes possible for a plurality of data relay apparatuses to share the history unnecessary condition. Next, a second embodiment of the present invention will be described. In the second embodiment, data requested by a data acquisition request output periodically is not stored in the data relay device.

In the WWW data, while the contents of the data are displayed, such as a so-called banner advertisement,
Some devices change an image at a fixed time interval. Among them, there is a method in which a client requests data corresponding to an image from a server at regular intervals, and rewrites the image with the returned data. When displaying such a page via the data relay device, a problem occurs. That is, the page for automatically loading an image requests image data to the data relay device while the page is open, so that the user can actually browse the page while the page is being displayed. Even if not
Image data will be stored in the data relay device,
Useless data for the user is stored in the data relay device.

This problem can be avoided by preventing the data corresponding to the data acquisition request transmitted periodically from the client from being held in the data relay device. Therefore,
A data relay device having the following configuration can be considered.

FIG. 5 is a block diagram showing a system configuration according to the second embodiment of the present invention. This configuration is
Since the configuration is the same as that of the first embodiment except for the configuration of the data relay device 100, the same components are denoted by the same reference numerals and description thereof is omitted (this is the same in other embodiments described later). ).

The data relay device 100 includes the request analysis unit 10
1, a data request unit 102, a name analysis unit 103, a history management unit 104, a history storage unit 105, an output unit 106, and a log storage unit 107. Here, the data request unit 10
2. The functions of the name analysis unit 103, the history storage unit 105, and the output unit 106 have the same functions as the components of the same name in the data relay device 50 of the first embodiment shown in FIG. I have. Other than that, the request analysis unit 101, the history management unit 104, and the log storage unit 107 have the following functions.

The request analysis unit 101 has the following functions in addition to the functions of the request analysis unit 51 in the first embodiment. That is, when a data acquisition request for relaying data is received, the log information is stored in the log holding unit 107 as log information in association with the time information of the received time, the data name, and the host name.

The history management unit 104 has almost the same function as the history management unit 54 in the first embodiment, but has a function of determining whether or not the history unnecessary condition is satisfied. Has the following functions instead of. That is, when the data acquisition request is a data relay request, the latest three pieces of log information corresponding to the name of the host on which the client that has output the data acquisition request is executed are extracted from the log holding unit 107. . Then, based on the time information included in the extracted log information, it is determined whether or not a data acquisition request for data with the same name has been output from the same host at regular time intervals. If a data acquisition request is issued at regular time intervals, it is determined that the data relayed in response to the data acquisition request is unnecessary data such as a banner advertisement, and the history information of the data is Do not keep.

The log holding unit 107 holds time information, data names, and host names in association with each other. Here, the user is required to enter the data 6 corresponding to the data name “url1”.
In order to browse 2, the client 41a transmits a data acquisition request to the data relay device 100. At this time, the data acquisition request transmitted by the client 41a is:
These are:

FIG. 6 is a diagram showing an example of a data acquisition request transmitted by a client. This data acquisition request 82
Is represented by header information transmitted by the client 41a by HTTP. The data acquisition request 82 has the description of “host-name: H1” in addition to the description of the same contents as the data acquisition request shown in FIG.
“Host-name:” represents the host name on which the client 41a operates.

In the data relay device 100 that receives such a data acquisition request 82, the request analysis unit 101 analyzes the contents of the data acquisition request 82. As a result, it is determined that the request is a data relay request, and the data name "url
"1" is sent to the data request unit 102 and the history management unit 104. Further, the request analysis unit 101 stores the time at which the data acquisition request 82 was received, the data name, and the host name in the log holding unit 107 in association with each other. As a result, the contents of the log holding unit 107 are as follows.

FIG. 7 is a diagram showing an example of log information. As shown in the figure, the log storage unit 107 stores log information arranged in chronological order. Then, as the latest log information, the time T11 at which the data acquisition request 82 was received,
The data name “url1” and the host name “H1” are registered.

The data requesting unit 102 having received the data name from the request analyzing unit 101 obtains the data 62 corresponding to the data name from the WWW server 61 and passes the data 62 to the history management unit 104.

The history management unit 104 stores the received data 6
2 as output data, and based on the log information stored in the log storage unit 107, it is determined whether or not the history information should be stored. In this example, first, the log holding unit 107
From the log information held in the host name "H1",
The latest three pieces of log information whose data name is “url1” are extracted. The extracted log information is as follows.

FIG. 8 shows extracted log information. As described above, the log of the data acquisition request transmitted from the host 41 having the name “H1” at times “T02”, “T03”, and “T11” is extracted. These times are “T02 <T03 <T11”.

Next, the history management unit 104 calculates a time interval “K1” between “T02” and “T03” and a time interval “K2” between “T03” and “T11”. This can be expressed as follows.

[0067]

(Equation 1) Then, the history management unit 104 compares K1 and K2. If K1 and K2 are the same value, the history management unit 1
No. 04 does not store the data 62 corresponding to “url1” in the history holding unit 105. If K1 is different from K2, the history management unit 104 stores the time T11, the data name “url1”, and the content of the data 62 in the history holding unit 105 in association with each other.

The data 62 is passed to the output unit 106 regardless of whether history information is stored in the history holding unit 105, and transmitted to the client 41a by the output unit 106. In this way, the data relay device 100 can be configured not to hold data corresponding to a data acquisition request periodically issued from a client. For this reason, useless data such as a banner advertisement need not be stored in the data relay device 100.

In the above description, an example has been described in which it is determined that the period is the same when the past two time intervals are the same, but it is determined that the period is the case when the past three or more time intervals are the same. You may do it.

In the above description, an example in which the periodicity is determined each time a request is processed has been described. However, the name (URL) of the data once determined to be periodic is checked, and the next time it is checked. The URL with a check may be handled as a periodic request without determining the periodicity.

Also, an example has been described in which the client includes the host name in the data acquisition request. However, an identifier (eg, an IP address) uniquely assigned to the client and which can be uniquely identified on the network is included instead. Is also good.

Further, it is also possible to include a user name in the data acquisition request transmitted from the client and determine the periodicity of the data acquisition request only for the data acquisition request from the same user.

Next, a third embodiment of the present invention will be described. In the third embodiment, the determination of the periodicity of the time interval in the second embodiment is allowed. That is, in the second embodiment, K1 and K2
Data is not retained when the value of is the same,
In the third embodiment, data is not held if the difference between K1 and K2 is within an allowable range.

FIG. 9 is a block diagram showing a system configuration according to the third embodiment of the present invention. The data relay device 110 according to the present embodiment includes a request analysis unit 111, a data request unit 112, a name analysis unit 113, a history management unit 114, a history storage unit 115, an output unit 116, a log storage unit 117, and an allowable range storage unit. 118. Here, the functions of the request analysis unit 111, the data request unit 112, the name analysis unit 113, the history storage unit 115, the output unit 116, and the log storage unit 117 are respectively the data of the second embodiment shown in FIG. It has the same function as the component of the same name in the relay device 100. Other elements have the following functions.

The history management unit 114 has almost the same function as that of the history management unit 104 in the second embodiment, but the time intervals K1 and K2 have the same value. The following function is provided in place of the function of determining whether or not. That is, the difference between the values of K1 and K2 is
It is determined whether or not the value is within the value held in the allowable range holding unit 118.

The allowable range holding unit 118 holds, as an allowable range, a value indicating to what extent the difference between the values of the time intervals is less than or equal to a period when it is determined that the request is a periodic data acquisition request. The value of the allowable range is set in advance by the administrator of the data relay device 110.

FIG. 10 is a diagram showing an example of the contents held in the allowable range holding unit. In this example, 10 seconds is set as the allowable range. As a result, the difference between K1 and K2 becomes 10
If within seconds, the data acquisition request at that time is determined to have periodicity.

Here, the user enters the data name “url”
It is assumed that the client 41a transmits a data acquisition request (similar to the data acquisition request 82 shown in FIG. 6) to the data relay device 110 in order to browse the data 62 corresponding to "1". However, since the process is the same as that of the second embodiment except for the determination of whether or not the history information is to be held in the history management unit 114, the description is omitted.

The history management unit 114 includes the data request unit 112
, First, time intervals K1 and K2 are obtained by the above equation (1). Then, the following equation

[0080]

S1 = | K2-K1 | (2) The difference S1 of the time interval is obtained. Then, it is determined whether or not the value of S1 is within the allowable range held in allowable range holding unit 118. Here, if S1 is smaller than the allowable range, the history management unit 114 determines that the data acquisition request transmitted from the client 41a is a periodic request,
The data 62 corresponding to “url1” is not held.

If S1 is larger than the value of the allowable range held by the allowable range holding unit 118, the history management unit 114 determines that the data acquisition request transmitted from the client is not a periodic request, and The data name "ur
l1 ”and the contents of the data 62,
15 is stored.

In this way, even when data acquisition requests are not transmitted at exactly the same cycle, the data relay device can determine the periodicity of those requests. Next, a fourth embodiment will be described. In the fourth embodiment, the periodicity of a data acquisition request is determined even when the URL is different.

In the above-described second and third embodiments, the case where data corresponding to a periodic request for the same data name (URL) is not held has been described. However, some banner advertisements used in WWW pages periodically execute a program included in the data of the page and request data of a different name periodically. Therefore, an example will be described in which, even if the names of the data are not exactly the same, if the server holding the data is the same, the request is determined to be a periodic request.

Since the system configuration of this embodiment is the same as that of the second embodiment shown in FIG. 5, this embodiment will be described using the reference numerals assigned to the respective elements in FIG. (Hereinafter, see FIG. 5). However, the function of the history management unit 104 is slightly different. That is, in the present embodiment, if the server name included in the log information data name is the same log information, the log information is extracted from the log holding unit 107 as a target for determining the periodicity of the data acquisition request.

Here, the user enters the data name “url”
Consider a case where a data acquisition request (similar to the data acquisition request 82 shown in FIG. 6) is transmitted from the client 41a to the data relay device 100 in order to browse the data 62 corresponding to "1". However, since the process is the same as that of the second embodiment except for the determination of whether or not the history information is to be held in the history management unit 104, the description is omitted.

It is assumed that the following log information is stored in the log storage unit 107. FIG. 11 is a diagram illustrating an example of a log held by the log holding unit. Although the URLs included in the log information in this example are all different, the log information at times T02, T03, and T11 is the same on the WWW server.

Returning to FIG. 5, upon receiving the data 62 from the data request unit 102, the history management unit 104 specifies the same WWW server name as the data acquisition request issued at time T11, and uses the same host name H1. Certain log information is extracted from the log holding unit 107. In this example, since the same WWW server is a request processed in T02, T03, and T11, the history management unit 104 calculates the time interval K1 between T02 and T03 and the time interval K2 between T03 and T11 by the formula (1). ) Is calculated.

Next, the history management unit 104 compares K1 with K2. If K1 and K2 are the same value, the history management unit 104 stores the data 62 corresponding to “url1”.
Is not stored in the history holding unit 105. If the values of K1 and K2 are different, the history management unit 104
1 and the name of the data “url1” and the content of the data 62 are stored in the history holding unit 105 in association with each other.

As described above, even when the data name included in the data acquisition request periodically issued from the client is different, the data relaying apparatus 100 according to the fourth embodiment transmits the data corresponding to the request. It can be kept from being held. Therefore, the data relay device 100
Eliminates the need to hold useless data.

Next, a fifth embodiment will be described. In the fifth embodiment, the lower limit of the cycle when data is not held is determined. When browsing a WWW page, if a plurality of images are included in the page, those images are sequentially requested to the data relay device. When a plurality of images having the same size are included in a page, a data acquisition request may be periodically transmitted to the data relay device. If the WWW server does not keep data corresponding to these periodic requests because it is the same, useful data may not be kept.

On the other hand, there are few banner advertisements that request images one after another at intervals of several seconds, and many request the next image after a certain time has elapsed. Based on these differences, an example will be described in which data retention in the data relay device is controlled by the length of the cycle.

FIG. 12 is a block diagram showing a system configuration according to the fifth embodiment of the present invention. The data relay device 120 according to the present embodiment includes a request analysis unit 121, a data request unit 122, a name analysis unit 123, a history management unit 124, a history storage unit 125, an output unit 126, a log storage unit 127, and an allowable range storage unit 128. , And a minimum period holding unit 129. Here, the request analysis unit 121 and the data request unit 12
2. Name analysis unit 123, history storage unit 125, output unit 12
6, the log holding unit 127 and the allowable range holding unit 128
Each has the same function as the component of the same name in the data relay device 110 of the third embodiment shown in FIG.
Other elements have the following functions.

The history management unit 124 has the following functions in addition to the functions of the history management unit 114 in the third embodiment. That is, it is determined whether or not the values of K1 and K2 are smaller than the minimum time held in the minimum cycle holding unit 129. If the value of K1 and K2 is smaller than the minimum cycle time, it is determined that the data acquisition request at that time is not a periodic request even if the difference between K1 and K2 is within the allowable range.

The minimum cycle holding section 129 holds the minimum time of the cycle. For example, the minimum cycle holding unit 129 holds the following data. FIG. 13 is a diagram illustrating an example of data held in the minimum cycle holding unit. In this example, the minimum time of the cycle is set to 3 minutes.

Here, the user enters the data name “url”
It is assumed that the client 41a transmits a data acquisition request (similar to the data acquisition request 82 shown in FIG. 6) to the data relay device 120 in order to browse the data 62 corresponding to "1". However, since the process is the same as that of the third embodiment except for the determination on whether or not the history information is to be held in the history management unit 124, the description is omitted.

As in the third embodiment, the history management unit 124 calculates S1 according to equation (2), and if S1 is smaller than the value of the allowable range held in the allowable range holding unit 128, K1 It is determined whether or not and K2 are smaller than the time held by the minimum period holding unit 129.

If either K1 or K2 is larger than the minimum cycle, the history management unit 124 determines that the request is periodic, and does not store the data 62 corresponding to "url1" in the history holding unit 125. .

If K1 and K2 are the same as the minimum period,
When the request is smaller than the minimum cycle, the history management unit 124 determines that the request is not periodic, and stores the time T11, the data name “url1”, and the data content in the history holding unit 125 in association with each other.

In this way, even if the requests transmitted from the client at short intervals become incidental periodically,
It is determined that the request is not a periodic request, and the history information can be held in the data relay device 120.

Next, a sixth embodiment will be described.
In the sixth embodiment, the upper limit of the cycle when no data is stored is determined. Recently, an example of automatically downloading pages on the WWW using automatic patrol software has been increasing. Since such software also periodically sends a request to the data relay device, it is difficult to distinguish the request from a request such as a banner advertisement. However, requests that go around once a day can be distinguished by not judging a long cycle as periodic. Therefore, an example will be described in which data corresponding to a long periodical data acquisition request is stored in the history storage unit.

FIG. 14 is a block diagram showing a system configuration according to the sixth embodiment of the present invention. The data relay device 130 according to the present embodiment includes a request analysis unit 131, a data request unit 132, a name analysis unit 133, a history management unit 134, a history storage unit 135, an output unit 136, a log storage unit 137, and an allowable range storage unit 138. , And a maximum period holding unit 139. Here, the request analyzing unit 131 and the data requesting unit 13
2. Name analysis unit 133, history storage unit 135, output unit 13
6, the log storage unit 137 and the allowable range storage unit 138
Each has the same function as the component of the same name in the data relay device 110 of the third embodiment shown in FIG.
Other elements have the following functions.

The history management section 134 has the following functions in addition to the functions of the history management section 114 in the third embodiment. That is, it is determined whether or not the values of K1 and K2 are longer than the maximum time stored in the maximum cycle storage unit 139. K over maximum time
If the value of 1 and K2 is large, it is determined that the data acquisition request at that time is not a periodic request even if the difference between the values of K1 and K2 is within an allowable range.

The maximum cycle holding section 139 holds the maximum time of the cycle. For example, the maximum cycle holding unit 139 holds the following data. FIG. 15 is a diagram illustrating an example of data held in the maximum cycle holding unit. In this example, one hour is set as the maximum cycle time.

Here, the user enters the data name “url”
It is assumed that the client 41a transmits a data acquisition request (similar to the data acquisition request 82 shown in FIG. 6) to the data relay device 130 in order to browse the data 62 corresponding to "1". However, the process is the same as that of the third embodiment except for the determination of whether or not the history information is to be held by the history management unit 134, and thus the description is omitted.

As in the third embodiment, the history management unit 134 calculates S1 according to equation (2), and if S1 is smaller than the value of the allowable range held in the allowable range holding unit 138, K1 It is determined whether or not and K2 are longer than the time held by the maximum cycle holding unit 139.

If either K1 or K2 is smaller than the maximum cycle, history management section 134 determines that the request is periodic, and does not store data 62 corresponding to "url1" in history holding section 135. .

If K1 and K2 are the same as the maximum period,
When the request is longer than the maximum cycle, the history management unit 134 determines that the request is not periodic, and stores the time T11, the data name “url1”, and the data content in the history holding unit 135 in association with each other.

In this manner, for a periodic request having a long cycle such as a request from the automatic patrol software, data corresponding to the request can be held in the data relay device.

Next, a seventh embodiment of the present invention will be described. In the seventh embodiment, a command can be issued from a client to always save relayed data regardless of a history unnecessary condition or a cycle of a data acquisition request.

In the embodiments described above, an example in which the history management unit determines that the history information is not held and the history information is not held in the history holding unit has been described. May be a user. Therefore, it is desirable that the relayed data can be stored in response to a command from the client even if the criteria for not retaining the history information are satisfied. Therefore, an example will be described below in which the data relay device holds the history information when the request from the client includes the information to save the history.

In this embodiment, the following functions are added to the request analysis unit and the history management unit in each of the above embodiments. In the following description, it is assumed that a system having the same configuration as that of the first embodiment is used.
The description will be made using the reference numerals shown in FIG.

The request analysis section 51 extracts data holding necessity information from a data acquisition request for relaying data, and passes it to the history management section 54. When it is specified in the data holding necessity information that data should be held, the history management unit 54 always writes the contents of the relayed data to the history management unit 5.
5 is stored.

Here, the user transmits a data acquisition request to the data relay device 50 from the client 41a in order to browse the data 62 corresponding to "url1".
At this time, the data acquisition request transmitted by the client 41a is as follows.

FIG. 16 is a diagram showing a data acquisition request including a data storage instruction. This data acquisition request 83
This is header information transmitted by the client 41a by HTTP. In this, "save-log: true" indicates that the data relay device requests to retain history information.

Returning to FIG. 2, the data relay device 50
The request for data corresponding to "rl1" is relayed to the WWW server 61. The WWW server 61 returns data 62 corresponding to “url1”. The details of this processing are the same as in the first embodiment, and thus will not be described here.

The data relay device 50 stores a history unnecessary condition when data is not held in advance in the history unnecessary condition holding unit 57.
To hold. An example of the history unnecessary condition held by the history unnecessary condition holding unit 57 is shown below.

FIG. 17 is a diagram showing an example of the history unnecessary condition held by the history unnecessary condition holding unit. The first condition is that “data is not held when the data name is“ url1 ”. That is.

The second condition is that "data is not held when the keyword" banner "or" banner "is included in the data name. That is. The third condition is that "if the server holding the data is www.aaa.bbb, the data is not held."

Here, the data requesting unit 52 that has received the data 62 passes the received data 62 to the history management unit 54. At this time, the data name “url1” conforms to the first condition in the history unnecessary condition of the history unnecessary condition holding unit 57. However, since the history information is specified to be held in the data acquisition request 83, the history management unit 54 does not check whether or not the history unnecessary condition is satisfied, and checks the time T11 and the data name "url1". Are stored in the history holding unit 55 in association with the data contents.

Here, the case where the history unnecessary condition is set has been described. However, even when the setting is made to judge the periodicity of the request, it is specified that the history information is retained in the data acquisition request. If so, the holding can be performed similarly.

Next, an eighth embodiment of the present invention will be described. In the eighth embodiment, a client is notified of whether or not the relayed data is stored in a data relay device.

In the embodiments described above, when the data relay device does not hold the history information of the data corresponding to the data acquisition request, the data relay device simply returns the data to the client as it is. However, in such a method, the user who transmitted the data acquisition request did not know whether the requested data was stored in the data relay device.

In order to avoid this problem, when data history information corresponding to a data acquisition request is not stored in the data relay device, the data relay device may include information indicating that data is not stored in the data. You may do it.

For example, when the page corresponding to "url1" is requested from the client and this page is not stored, the following description is added to the end of the page when the output unit outputs data. It may be.

FIG. 18 is a diagram showing additional contents when data is not stored. In this example, a description “this page was not stored” is added at the end of the content of the document 84 created in HTML.

When this data is sent to the client,
The contents are displayed on the screen of the display device. FIG. 19 is a diagram illustrating a screen example of the client. In the screen 90, there is a data content display section 91, and the content display section 9
At the bottom of 1, "This page was not stored" is displayed.

In this way, it is possible to inform the user that no data has been stored. In this example,
An example has been described in which information indicating that the content is not stored is added to the HTML document. However, when the data requested by the URL is an image, an image obtained by imaging the contents of FIG. The image may be combined with the requested image and returned to the client.

Also, an example has been described in which the data returned to the client includes information indicating that the data was not stored. However, in the protocol for returning data to the client, the information indicating that the data was not stored is returned. You may do so. For example, when returning data to the client,
The following header is added to the HTTP header.

FIG. 20 is a diagram showing additional contents of the header when no data is held. In this example, “store: false” is described in the header information 85. This header information 85 indicates that the data corresponding to the data acquisition request has not been stored in the data relay device.

As described above, if the information indicating that no data is stored is described in the header information, the information that the data is not stored in the data relay device can be transmitted to the client without changing the content of the data. Can tell.

Note that the above processing functions can be realized by a computer. In this case, the processing contents of the functions that the data relay device should have are described in a program recorded on a computer-readable recording medium, and the above processing is realized by the computer by executing the program on the computer. Is done. Examples of the computer-readable recording medium include a magnetic recording device and a semiconductor memory. If you want to distribute the market,
The program is stored and distributed in a portable recording medium such as a CD-ROM (Compact Disk Read Only Memory) or a floppy disk, or stored in a storage device of a computer connected via a network. It can also be transferred to a computer. When the program is executed by the computer, the program is stored in a hard disk device or the like in the computer, and is loaded into the main memory and executed.

[0132]

As described above, in the first data relay device according to the present invention, when the history unnecessary condition is satisfied, the relayed data is not stored in the history holding means, so that the unnecessary data is not stored. Can be prevented from being stored in the data relay device.

Further, in the second data relay device according to the present invention, the data relayed based on the periodic data acquisition request is not stored in the history holding means, so that unnecessary data is stored in the data relay device. Can be prevented from being accumulated.

Further, in the case of a computer-readable recording medium on which the first data relay program according to the present invention is recorded, if the history unnecessary condition is satisfied, processing for not storing the relayed data in the history holding means is performed. Since the described program is recorded, the computer can execute the program to realize a data relay device that does not store unnecessary data.

Further, in the computer-readable recording medium on which the second data relay program according to the present invention is recorded, processing is performed such that data relayed based on a periodic data acquisition request is not stored in the history holding means. Since the described program is recorded, the computer can execute the program to realize a data relay device that does not store unnecessary data.

[Brief description of the drawings]

FIG. 1 is a principle configuration diagram of the present invention.

FIG. 2 is a block diagram illustrating a system configuration according to the first embodiment of this invention.

FIG. 3 is a diagram showing an example of a history unnecessary condition.

FIG. 4 is a diagram illustrating an example of a data acquisition request transmitted by a client.

FIG. 5 is a block diagram illustrating a system configuration according to a second embodiment of this invention.

FIG. 6 is a diagram illustrating an example of a data acquisition request transmitted by a client.

FIG. 7 is a diagram illustrating an example of log information.

FIG. 8 is a diagram showing extracted log information.

FIG. 9 is a block diagram showing a system configuration according to a third embodiment of the present invention.

FIG. 10 is a diagram illustrating an example of content held in an allowable range holding unit.

FIG. 11 illustrates an example of a log held by a log holding unit.

FIG. 12 is a block diagram illustrating a system configuration according to a fifth embodiment of the present invention.

FIG. 13 is a diagram illustrating an example of data held in a minimum cycle holding unit.

FIG. 14 is a block diagram illustrating a system configuration according to a sixth embodiment of the present invention.

FIG. 15 is a diagram illustrating an example of data held in a maximum cycle holding unit.

FIG. 16 is a diagram showing a data acquisition request including a data storage instruction.

FIG. 17 is a diagram illustrating an example of a history unnecessary condition held by a history unnecessary condition holding unit.

FIG. 18 is a diagram illustrating additional content when data is not stored.

FIG. 19 is a diagram illustrating a screen example of a client.

FIG. 20 is a diagram illustrating additional contents of a header when data is not held.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 11 Data utilization means 12 Data supply means 12a Data 20 Data relay apparatus 21 History holding means 22 History unnecessary condition holding means 23 Request analysis means 24 Data request means 25 History management means 26 Output means

Claims (9)

[Claims] 1. A data relay device for relaying data between a data use unit that uses data obtained by request and a data supply unit that supplies held data in response to a request, wherein a history of the relayed data is provided. A history holding unit for holding information; a history unnecessary condition holding unit for storing a history unnecessary condition in which a condition for not holding history information in the history holding unit; and a data acquisition request from a data using unit. Analyzing whether the request is a data relay request or a history information acquisition request, if the data acquisition request is a data relay request, extract the data name from the data acquisition request; Request acquisition means for extracting data name and time information from the data acquisition request, wherein the data acquisition request relays data. In the case of a request, the request analysis means requests data corresponding to the name of the data extracted from the data supply means, and a data request means for receiving data transmitted from the data supply means in response to the request; If the acquisition request is a data relay request and the data acquisition request does not satisfy the history unnecessary condition, the data received by the data request unit, the name of the data, and the time at which the data relay process was performed Is stored in the history holding unit as history information in association with the time information, and the data received by the data requesting unit is used as output data. If the data acquisition request is a history information acquisition request, the request analysis is performed. History information matching the name and time information of the data extracted by the means is searched from the history holding means and included in the detected history information. Data output means, and output means for outputting the output data specified by the history management means to a data use means which is an output source of the data acquisition request. Data relay device. 2. A data relay device for relaying data between a data use unit that uses data obtained by request and a data supply unit that supplies held data in response to a request, wherein a history of the relayed data is provided. A history holding unit for holding information; and upon receiving a data acquisition request from the data using unit, analyze whether the data acquisition request is a data relay request or a history information acquisition request, and determine whether the data acquisition request is a data relay request. In the case, a request analysis unit that extracts a data name from the data acquisition request, and extracts the data name and time information from the data acquisition request when the data acquisition request is a history information acquisition request. A log holding unit that associates information included in the data acquisition request with time information indicating a request processing time and holds the information as log information; When the request is a data relay request, the data requesting unit requests data corresponding to the name of the data extracted by the request analyzing unit from the data supplying unit, and receives the data transmitted from the data supplying unit in response to the request. Means, the data acquisition request is a data relay request, and the presence or absence of periodicity of data access is determined based on log information stored in the log holding means, and it is determined that the access is not periodic. In this case, the data received by the data request unit, the name of the data, and the time information of the time at which the data relaying process was performed are stored in the history holding unit as history information in association with each other, and the data request unit receives the data. If the data acquisition request is a history information acquisition request, the name and time of the data extracted by the request analysis unit are output. History information matching the information, a history management unit that searches the history holding unit for the data included in the detected history information as output data, and a data use unit that is an output source of the data acquisition request. Output means for outputting the output data specified by the history management means. 3. The log management unit extracts, from the log storage unit, log information for a plurality of past times for data having the same name as the data acquisition request, and a time interval of time information added to the extracted log information. 3. The data relay device according to claim 2, wherein when is equal, the data access is determined to be a periodic data access. 4. An apparatus according to claim 1, further comprising an allowable range holding unit configured to hold an allowable value defining an allowable range when judging the uniformity of the time intervals, wherein the history management unit stores data having the same name as the data acquisition request. The log information is extracted from the log holding unit for a plurality of times in the past, and if the difference between the time intervals of the time information added to the extracted log information is within the allowable value, it is a periodic data access. 4. The data relay device according to claim 3, wherein the data relay device determines that: 5. The log management unit extracts, from the log holding unit, log information for a plurality of past times for data held in the same data supply unit as the data acquisition request.
3. The data relay device according to claim 2, wherein the presence or absence of periodicity is determined based on time information included in the extracted log information. 6. The history management unit according to claim 2, wherein when the period of the time interval is smaller than a preset minimum period, it is determined that the access is aperiodic.
The data relay device according to the above. 7. The system according to claim 2, wherein the history management unit determines that the access is aperiodic if the period of the time interval is longer than a preset maximum period.
The data relay device according to the above. 8. A computer-readable storage medium storing a data relay program for relaying data between a data use unit that uses data obtained by request and a data supply unit that supplies held data according to a request. In a possible recording medium, history holding means for holding history information of relayed data, history unnecessary condition storing means for storing a history unnecessary condition in which a condition for not holding history information is stored in the history holding means, and data from data using means. Upon receiving the acquisition request, it analyzes whether the data acquisition request is a data relay request or a history information acquisition request, and extracts the data name from the data acquisition request when the data acquisition request is a data relay request. When the data acquisition request is a history information acquisition request, the data name and time information are extracted from the data acquisition request. When the data acquisition request is a data relay request, the request analysis unit requests data corresponding to the name of the data extracted by the request analysis unit from the data supply unit, and transmits the data from the data supply unit in response to the request. Data request means for receiving the received data, the data acquisition request is a data relay request, and if the data acquisition request does not meet the history unnecessary condition, the data received by the data request means, The name of the data and the time information of the time at which the data relaying process was performed are stored in the history holding unit as history information in association with each other, and the data received by the data requesting unit is used as output data. In the case of an information acquisition request, history information matching the data name and time information extracted by the request History management means for making data included in the history information detected and detected from the holding means as output data, and outputting the output data specified by the history management means to the data use means which is the output source of the data acquisition request A computer-readable recording medium on which a data relay program is recorded, which causes a computer to function as output means. 9. A computer-readable recording medium storing a data relay program for relaying data between a data use unit that uses data obtained by request and a data supply unit that supplies held data in response to a request. In a possible recording medium, a history holding unit that holds history information of relayed data, upon receiving a data acquisition request from a data using unit, analyzes whether the data acquisition request is a data relay request or a history information acquisition request, If the data acquisition request is a data relay request, the data name is extracted from the data acquisition request.If the data acquisition request is a history information acquisition request, the data name is extracted from the data acquisition request. Request analysis means for extracting time information; associating information included in the data acquisition request with time information indicating request processing time; Log holding means for holding as data, when the data acquisition request is a data relay request, requests data corresponding to the name of the data extracted by the request analysis means to the data supply means; Data request means for receiving data sent from the supply means, wherein the data acquisition request is a data relay request, and the presence or absence of data access periodicity is determined based on log information stored in the log holding means. If it is determined that the access is not the same type of periodic access, the data received by the data request unit, the name of the data, and the time information of the time at which the data relay process was performed are associated with each other, and Storing the data in the holding unit, and using the data received by the data request unit as output data, wherein the data acquisition request is a history information acquisition request; In such a case, history information matching the name and time information of the data extracted by the request analysis means is searched from the history holding means, and the history management means which uses the data included in the detected history information as output data An output unit that outputs the output data specified by the history management unit to a data use unit that is an output source of the data acquisition request. Recording medium.