JP2000200233A - Device and method for data acquisition notification and recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To shorten the time needed for a client to receive data from a server and to effectively use network resources by informing the client that compressed data are accessed or accessible. SOLUTION: The control unit 12 is connected to the connection destination that a URL indicates through a transmission and reception device 13 and starts downloading data to be obtained. The data are stored temporarily in a storage device 10. The control unit 12 compresses and stores the temporarily saved data. In this case, when the compression of the data is completed, the temporarily saved data are deleted from the storage device 10. Then, an indication is so made that when the client makes a connection again through the transmission and reception device 13, data which are compressed thereafter can be downloaded by the client. When a downloading request is accepted from the client, the control unit 12 allows the client to download the compressed data through the transmission and reception device 13 and the compressed data are deleted from the storage device 10.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION The present invention relates to a WWW (World
For proxy acquisition technology that acquires data on behalf of the client, such as the Wide Web, more specifically, by compressing the acquired data, the aim is to reduce the time required for the client to receive this data. is there.

[0002]

2. Description of the Related Art In a server-client environment, a client routinely downloads, for example, hypertext or graphics from a WWW server. In addition, software that circulates a required address automatically and stores required data in a local storage device is executed on a client.

[0003] The use of such automatic patrol software may be performed by a client constantly connected to the LAN, or may be performed by so-called dial-up connection from homes only when necessary. In the latter case, it is generally connected to the Internet via a service provider using a telephone line. And they pay a usage fee according to the connection time.

[0004]

However, while the automatic patrol software as described above downloads everything as set, it cannot disconnect from the Internet and pays a high line usage fee. There is a problem that must be. Another problem is that raw data is downloaded as it is, and during this time, resources such as computers and lines continue to be squeezed, which is a problem that occurs not only in the Internet but also in the server / client environment in general. But also.

[0005] Therefore, an object of the present invention is to reduce the time required for a client to receive data from a server and to enable effective use of network resources.

[0006]

SUMMARY OF THE INVENTION
According to the first aspect of the present invention, an input unit that receives a URL of data to be acquired and a domain indicated by the URL of the input unit are accessed (hereinafter, referred to as accessing the URL of the input unit) to acquire the data. An acquisition unit that issues a request and stores received data in a cache memory; a compression unit that compresses data in the cache memory and stores it in a storage device; and enables and accesses the compressed data. This is achieved by providing a data acquisition notification device including a notification unit that notifies a client of the fact.

The data acquisition notifying device acts as a server when the input unit accepts the URL of the data to be acquired, and the acquisition unit accesses the URL to issue the data acquisition request, and stores the received data in the cache memory. When storing, it acts as a client. Also, after the compression unit compresses the received data, the notifying unit enables access to the compressed data and acts as a server when notifying the client that access is possible.

[0008] The client connects to the server and downloads the compressed data based on the notification. Therefore, the client can temporarily disconnect the connection after the data acquisition notification device receives the URL of the data to be acquired. Then, when the client connects to the data acquisition notifying device again, desired data can be delivered as compressed data in a shorter time, thereby enabling effective use of resources. The client then decompresses and uses the compressed data.

According to a second aspect of the present invention, in the data acquisition notifying apparatus of the first aspect, the notifying unit generates a hypertext in which a link to the compressed data is described and presents the hypertext to a client. Part is provided.

[0010] When the compression of the received data is completed, the data acquisition and notification device generates a hypertext for client notification by the WWW server unit. First, the client connects to the WWW server unit, confirms the notification with the WWW browser, and subsequently receives the desired data as compressed data. Therefore, the desired data can be delivered to the client in a shorter time.

According to a third aspect of the present invention, in the data acquisition notifying device of the first aspect, the notifying unit sends an electronic mail describing a URL for accessing the compressed data to the client. A mail transmission unit is provided.

When the client receives this e-mail, it can access the URL of the compressed data described therein and receive the desired data as compressed data. Therefore, it is sufficient that the client waits until the notification by the e-mail is received, and the desired data can be delivered in a shorter time.

Next, according to the invention of claim 4, a client accesses a URL given via a network to acquire required data, compresses the data after acquiring the data, and downloads the compressed data. In addition, the above problem is solved by a data acquisition notifying method characterized by notifying a client of this state.

Therefore, the client can temporarily disconnect the connection after notifying the URL of the data to be acquired. Then, based on the notification, desired data can be received as compressed data in a shorter time. Therefore, it is possible to effectively use resources without imposing a burden on the client.

According to a fifth aspect of the present invention, in the data acquisition notifying method according to the fourth aspect, the client is notified by presenting a hypertext with a link to the compressed data. .

Therefore, it is possible to make the client confirm the notification with the WWW browser and receive the desired data in a shorter time.

According to a sixth aspect of the present invention, in the data acquisition notifying method of the fourth aspect, the client is notified by sending an electronic mail describing a URL for accessing the compressed data to the client. Features.

Therefore, the client only has to wait until receiving the notification by the e-mail, and the desired data can be delivered in a shorter time.

Next, a seventh aspect of the present invention is a recording medium storing a program for causing a computer including an acquisition unit for accessing a URL of data to be acquired to acquire required data to process the data. Receiving the URL of the data to be acquired at the input unit, and
RL is accessed, the data acquisition request is issued, the received data is stored in the cache memory, the data in the cache memory is compressed by the compression unit and stored in the storage device, and the notifying unit accesses the compressed data. And a program for causing a computer to perform a process of notifying a client that access is possible.

The computer loads a program for processing data to be acquired from a recording medium and executes the program. The contents of this execution are as follows: a client accesses a URL provided via a network to acquire corresponding data, compresses the data after acquiring the data, makes the compressed data downloadable, and Is to notify the client. Therefore,
After notifying the URL of the data to be acquired, the client can temporarily disconnect the connection. Then, based on the notification, desired data can be received as compressed data in a shorter time. As a result, resources can be effectively used. These benefits are offered to clients.

According to an eighth aspect of the present invention, in the recording medium on which the program according to the seventh aspect is recorded, the notifying process generates and presents a hypertext in which a link to the compressed data is described by displaying the hypertext. Is to be notified.

Therefore, it is possible to make the client confirm the notification with the WWW browser and receive the desired data in a shorter time.

According to a ninth aspect of the present invention, in the recording medium storing the program of the seventh aspect, the notifying process includes transmitting an electronic mail describing a URL for accessing the compressed data to the client. Notify the client.

Therefore, the client only has to wait until receiving the notification by the e-mail, and the desired data can be delivered in a shorter time.

The recording medium on which the program is recorded is a CD
-ROM, hard disk, flexible disk, R
The concept includes OM, RAM, memory card, paper tape, punch card, and the like. In addition to a recording medium on which a program is recorded in a state that can be directly executed by a computer, for example, a recording medium on which a program which can be executed by being installed from a CD-ROM to another recording medium such as a hard disk, or data is stored. Encoding,
It also includes a recording medium on which an encrypted or compressed program is recorded. The reason for including the RAM is that the program received via the network may be loaded on the RAM. URL is HTML
Unique <A HREF="scheme name://domain name/path name/file name"></A> written in the anchor tag of the format, and the remote mounted directory and the file name placed there A general address that points to

[0026]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described with reference to the drawings, but the present invention is not limited to these embodiments. In the following embodiment, a server having data to be acquired by a client is referred to as a server.
In order to distinguish it from the role of the server of the present invention, it is referred to as another server.

(First Embodiment) FIG. 1 shows an overall configuration of a data acquisition and notification device according to an embodiment of the present invention. The input device 1 includes a keyboard for performing various operations in the data acquisition and notification device.
The display device 11 is for displaying various setting operations from the input device 1 and the results thereof. This data acquisition notification device acts as a server when requested to download and compress data from a client, and when transmitting compressed data to a client, and as a client when connecting to another server and downloading data. At this time, the transmission / reception device 13 mediates communication with a client or another server. The storage device 10 temporarily stores data downloaded from another server, and stores the data after the control device 12 compresses the data, at least until the data is downloaded to the client. The control device 12 controls these devices.

This data acquisition notification device is always connected to a network such as the Internet via the transmission / reception device 13. When the control device 12 receives a connection request from a client via the transmission / reception device 13,
It prompts the client to enter the URL of the data to be acquired, and accepts this URL.

Subsequently, the control device 12 connects to the connection destination indicated by the URL via the transmission / reception device 13, and starts downloading data to be acquired. The downloaded data is temporarily stored in the storage device 10. This part of the storage device 10 is generally called a cache memory. When the download is completed, disconnect the connection.

Subsequently, the control device 12 compresses the temporarily stored data and stores it. In this embodiment, the data temporarily stored when the data compression is completed is stored in the storage device 1.
It has been deleted from 0.

Thereafter, the compressed data is presented so that the client can download it when the client connects again via the transmission / reception device 13. Then, upon receiving a download request from the client, the control device 12 causes the client to download the compressed data via the transmission / reception device 13, and deletes the compressed data from the storage device 10 when the processing is completed.

Normally, when a client directly exchanges data with another server to obtain data, the data is raw data. Therefore, there is a problem that the client takes a long time to download the data. The data acquisition / notification device of the present invention downloads the data on behalf of the device, and provides the client with a compressed version of the downloaded data.

In this embodiment, data downloaded from another server is simply compressed. However, if there are a plurality of download data, the data may be stored and compressed as in the embodiment described later. For example, a case where image data called from a hypertext is downloaded together with the hypertext, or a case where a plurality of hypertexts having a hierarchical structure are downloaded. Further, at this time, the data may be rewritten with hypertext links according to the desired directory structure on the client side, and then archived and compressed. The next time the client connects, it notifies the client that the compressed data is ready, and the link to the compressed data is as if the compressed data was there. Is generated and presented. The connection with the client may be left to the client, or may be cut off when the URL has been received or the compressed data has been transmitted. The display device 11 may display the exchange with the client.

In addition, it has been realized that the input unit has a function of receiving an electronic mail and reading out a URL written therein. Alternatively, reception by telnet, telephone reception and voice recognition may be used. It is also possible to provide dedicated software to clients. The compression unit is
In this embodiment, this is realized by the control device 12, but the compression algorithm and the like are arbitrary. The notification unit has a function of transmitting an e-mail, and the like, but a function of transmitting a facsimile can also be realized. A push technology called so-called smart pull may be adopted. The compressed data is downloaded using WWW or ftp, but other methods are also possible.
Further, as described later, the user may be prompted to input an ID or password when connecting to the client.

The data acquisition notifying device of this embodiment exchanges data with another server to acquire data.
Further, an apparatus has been realized that accepts a keyword together with a URL from a client, causes another server to transmit a result searched by the keyword, receives and compresses the result, notifies the client, and downloads the compressed data. I have.

(Second Embodiment) Next, FIG. 2 shows a hardware configuration in a case where the data acquisition notifying device of FIG. Also, FIGS. 3, 6, 8, and 9
The program 30 of each part of the data acquisition notification program
33 are shown in a flowchart. Note that the data acquisition notification device 4 of FIG. 1 may be configured by hardware logic without using a CPU.

A memory 20, a hard disk 10 as a storage device, a keyboard / mouse 1 as an input device, a display 11 as a display device, a LAN card 13 as a transmitting / receiving device, and a CD-ROM drive 22 are connected to the CPU 2. I have. The hard disk 10 includes an operating system OS3, a URL reception server program 30, a data reception client program 31, and a data compression program 3 which constitute a data acquisition notification program.
2. Notification and transmission server program 33 are stored. These programs are stored in a CD-ROM drive 2
2 is installed from the CD-ROM 23 via the CD-ROM 23.

FIG. 4 shows a state in which the client 5 is connected to the data acquisition notifying device 4 via the Internet. FIG. 5 shows a display screen displayed on the client-side display D prepared by the data acquisition notifying device 4. Note that the description here assumes that the data that the user of the client wants to acquire is a WWW page. The processing here is handled by the URL reception server program 30.

The data acquisition notification device 4 and the other server 6
Both are always connected to the Internet. Now, when the client 5 is connected to the Internet through a dial-up connection and establishes a connection to the data acquisition and notification device 4, the data acquisition and notification device 4 acts as a server. A connection between the two is established (step S1), a connection destination URL which is an address indicating a specific WWW page owned by the other server 6 is received (step S2), and the connection between the two is disconnected (step S3). Before disconnecting the connection in step S3, the connection destination U
It may be inquired whether or not the user wants to set the RL, and if so, the input of the connection destination URL may be accepted again. In step S1, the activated browser 7 is displayed on the display D of the client 5.
The URL of the data acquisition notifying device 4 is input to the address bar 71 of the device, and the data acquisition notifying device 4 is connected. In step S2, the HTML document 70 transmitted by the data acquisition notifying device 4 is displayed on the browser 7. This HT
The ML document 70 is provided with an input form 72 of a connection destination URL, and the client user writes the URL of the WWW page to be obtained here and presses an OK button to display the URL of the WWW page to be obtained.
The RL is transmitted and received by the data acquisition notification device 4. In FIG. 3, reference numeral 40 indicates the flow of URL data at this time. The received URL data is stored in the temporary storage of the hard disk 10.

The HTML document 70, that is, the display of the browser 7, will be described in more detail. The user of the client does not merely write the URL in the input form 72, but also displays the URL linked from the first WWW page to be obtained. It is possible to set the depth, whether the link destination is only within this site, whether it is possible outside the site, whether to access this time only, or to set a schedule. Also, here, you will be asked to enter the user ID and password of the client,
At the time of downloading compressed data to be described later, preparation is made for user authentication for access to the user-specific HTML document 76 in FIG.

Now, the data acquisition notifying device 4 and the other server 6
Are connected to the Internet, but the client 5 has already disconnected the connection to the data acquisition notification device 4 and the Internet (FIG. 7). If the data acquisition / notification device 4 has established a connection to the other server 6 now, the data acquisition / notification device 4 behaves as a client this time. That is, the data acquisition notifying device 4 connects to the other server 6 based on the URL data previously input by the client 5 (step S4), and starts downloading a required WWW page (step S5). When the download is completed as set (step S6), the connection with the other server 6 is disconnected (step S7), and the process ends. FIG.
Reference numeral 60 indicates the flow of the WWW page at this time. The received WWW page is stored in the temporary storage of the hard disk 10. The processing here is performed by the data receiving client program 31.

Subsequently, as shown in FIG. 8, the data compression program 32 archives and compresses the WWW page, which is the download data stored in the temporary storage of the hard disk 10, and stores it in the hard disk 10 (step S8). Thereafter, a notification HTML document with a link to the archived compressed data is generated in preparation for reconnection of the client 5 (step S9). As described above, in this embodiment, the notification is made by the WWW server of the data acquisition
This is performed by displaying on the WW page that the compressed data can be downloaded at any time. Conversely, the client user sees this WWW page and receives a notification that the compressed data can be downloaded.

FIG. 10 shows a state in which a client who has been looking for a suitable time has connected to the data acquisition and notification device 4 via the Internet. In this case, the client is connected by inputting the download URL of the WWW server of the data acquisition and notification device 4 into the address bar 74 of the browser 7. Reference numeral 74 denotes an address bar to which a URL for download is input. At the time of this connection, the user of the client is made to input a user ID and a password, and the user is authenticated by comparing it with the one received earlier. FIG. 11 shows a display D on the client side prepared by the data acquisition notifying device 4.
3 shows a display screen to be displayed. The HTML document 73 transmitted by the data acquisition notification device 4 is displayed on the browser 7. In the HTML document 73, a link 75 to the archived compressed data is displayed. Here, a link 75 to two archived compressed data desired by the user of the client is displayed. The notification and transmission server program 33 is in charge of this process.

FIG. 9 shows a notification and transmission server program 33.
It is a flowchart regarding the process of. Client 5
Is connected to the Internet via a dial-up connection and establishes a connection to the data acquisition and notification device 4, the data acquisition and notification device 4 behaves again as a server. Establish a connection between them (step S10),
An HTML document 73 corresponding to the URL for download input to the address bar 74 by the client is displayed.
When the client selects the link 75 to the archived compressed data, the archived compressed data is downloaded to the client 5 (step S11). Symbol 4 in FIG.
Reference numeral 1 denotes the flow of archived compressed data at this time. When the transmission of this data to the client 5 is completed (step S12), the connection between them is disconnected (step S12).
13). Before disconnection of the connection in step S13, if links 75 to a plurality of archived compressed data are indicated, it is asked whether the user wants to download continuously.
If desired, it may be possible to continue further. Thereafter, in this embodiment, the archived compressed data transmitted to the client is deleted from the hard disk 10. On the client side, the received archived compressed data is decompressed and restored for use.

(Third Embodiment) Next, FIGS.
Reference numeral 5 denotes a third embodiment of the present invention. The main purpose of this embodiment is basically the same as that of the second embodiment, except that the user wants to use e-mail to notify the client that compressed data can be downloaded.

Now, when the client 5 is connected to the Internet through a dial-up connection and establishes a connection with the data acquisition / notification device 4, the connection between the two is established (step S14), and the connection destination URL desired by the client user is established. The e-mail address of this user is accepted (step S15), and thereafter, the connection between them is disconnected (step S16). According to FIG. 13, in step S14, the running browser 7 is displayed on the display D of the client 5, and the URL of the data acquisition notifying device 4 is input into the address bar 71 of the browser 7 to input the data. It is connected to the acquisition notification device 4. In step S15, the HTML document 76 transmitted by the data acquisition notifying device 4 is displayed on the browser 7. The HTML document 70 is provided with an input form 72 for a connection destination URL, and a new input form 77 for receiving a user's e-mail address is provided. The user of the client writes the URL of the WWW page to be obtained and the e-mail address in these forms, and presses the OK button. Then, the URL of the WWW page to be obtained and the e-mail to which the notification is sent are sent. The address is transmitted and accepted by the data acquisition and notification device 4. The received URL data and e-mail address are stored in the temporary storage of the hard disk 10. FIG. 12 shows a flowchart of the URL and the e-mail address reception server program.

Thereafter, the data acquisition notifying device 4 downloads required data and compresses the data. In the latter case, the WWW page, which is the download data stored in the temporary storage of the hard disk 10, is archived and compressed, and stored in the hard disk 10 (step S1).
7) Next, a notification HTML document with a link to the archived compressed data is generated (step S18), the download is completed, the archived compression is completed, and the data can be downloaded at any time. To notify
An e-mail for notification is transmitted to the e-mail address of the user (step S19). FIG. 14 is a flowchart of this process, and FIG. 15 shows a transmission path of the notification e-mail 42.

The user who has received the notification e-mail downloads the desired archived compressed data through the path shown in FIG. 10, as described in the second embodiment. Since this data is compressed, the client 5
As compared with the time required for directly receiving data from the other server 6, the time can be reduced substantially corresponding to the compression ratio, and the Internet resources can be effectively used. Also, since the notification is made by e-mail, unlike the second embodiment, the user of the client 5 connects to the data acquisition and notification device 4 at an appropriate time to determine whether or not downloading is possible. This saves the user the trouble of confirming, and is extremely convenient for the user.

(Fourth Embodiment) In both the second and third embodiments, first, the client 5 is connected to the data acquisition and notification device 4 via the Internet, and the client user wants to acquire the data to be acquired. URL
Is received by the URL reception server program 30. On the other hand, in the third embodiment, the notification is performed by transmitting a notification e-mail to the client 5. In other words, it is thought that if an electronic mail is used for receiving a URL of data that the user wants to acquire, the convenience for the user at the time of application is increased.

FIG. 16 shows a processing flowchart in the URL reception server program by electronic mail. Note that a block diagram of the URL reception server program by e-mail is not shown. An e-mail in which the URL of the data that the user of the client 5 wants to obtain is written in the body is transmitted to the e-mail address of the data acquisition notification device 4. Then, the data acquisition notifying device 4 receives this e-mail (step S
16) Extract the URL of the data that the user wants to acquire from the body of the e-mail, that is, the connection destination URL (step S17), and add it to the queue (step S1).
8). The URL added to the queue is the next process, that is, waiting for the turn of the download process from the other server 6.

(Fifth Embodiment) The data that the user of the client wants to acquire is stored in the server 6 which is another server.
Is owned by For example, when the other server 6 owns a plurality of hypertexts having a hierarchical structure, such data is often stored in the other server 6 in different directories. At this time, the format of the link is HTM
<A HREF="scheme name://domain name/path name/file name"></A> represented by an anchor tag in L format. When this is brought to the client 5 as it is, if the domain name is left, if the data of the link destination is put on its own hard disk, it is necessary to look at the other server 6 without any trouble. Things like going happen. Therefore, after rewriting the hypertext link according to the desired client-side directory structure of the data, the archive compression is performed.
This is the fifth embodiment. As a result of this processing, all link destinations are in the directory on the client side.

The data acquisition notifying device 4 connects to the other server 6 based on the URL data previously input by the client 5, and downloads a required WWW page. Thereafter, as shown in the flow chart of the link rewriting server program in FIG. 17, the link between the download files is rewritten according to the directory structure on the client side (step S23), and these WWW pages are archived and compressed. Then, the data is stored in the hard disk 10 (step S24), and a process of generating an HTML document for notification with a link to the archived compressed data is performed in preparation for reconnection of the client 5 (step S25). As described above, in this embodiment, all link destinations are rewritten according to the directory structure on the client side. If it is inconvenient to notify the data acquisition notifying device 4 of the directory structure of the client 5 in advance, a certain directory structure is determined, and based on this, a predetermined directory structure is determined in step S23. Rewriting may be performed, and the client 5 may correspond to the rewriting.

(Sixth Embodiment) In the first place, the present invention
It is an object of the present invention to reduce the time required for a client to receive data from a server and to make effective use of Internet resources. Then, for example, when a client user wants to download a certain WWW page, if the WWW page is linked with moving image data of a huge file size, the download may cause a heavy load on the network. Therefore, if the client user desires, such a moving image file may not be downloaded. This goes beyond just video files.

In this embodiment, the data acquisition notifying device 4 connects to the other server 6 based on the URL data previously input by the client 5 and downloads a required WWW page. Each file is checked (step S26), and whether or not the file is a moving image file is identified (step S27), and all files that are not moving image files are downloaded (step S28). At the same time, the operation of replacing the moving image file with the icon prepared in the hard disk 10 is performed (step S29). The icon may be a still image or a moving image. If it is decided that the same icon is always used, storing this icon on the client 5 side eliminates the need to send the icon to the client 5 every time. FIG. 18 shows a flowchart of the icon replacement server program.

(Seventh Embodiment) Next, the data acquisition notifying apparatuses of the first to sixth embodiments exchange data with another server to acquire data. May be transmitted to another server, and the result of the search using this keyword may be transmitted. The result may be received and compressed, and the client may be notified to download the compressed data. In this case, the other server has a search engine, but in some cases, the search result may be hundreds or thousands. It is desirable that such search result list data be transmitted after being compressed. This is because the load on the network can be reduced.

FIG. 19 illustrates the hard disk 10 in this embodiment. CPU2, memory 2
0, a keyboard / mouse 1 as an input device, a display 11 as a display device, a LAN card 13 as a transmitting / receiving device, a CD-ROM drive 22, etc.
Followed the second embodiment. The hard disk 10 includes an operating system OS3, a keyword reception server program 34 constituting a data acquisition notification program, and a keyword search client program 3
5, a search result list compression program 36 and a notification and transmission server program 37 are stored. These programs are installed from a CD-ROM 23 via a CD-ROM drive 22 (not shown).

The keyword receiving server program 34
A client 5 is connected to the data acquisition notifying device 4 via the Internet, and accepts a keyword that the user of the client wants to search. The keyword search client program 35 connects the data acquisition and notification device 4 to the other server 6, passes the keyword to the other server 6, disconnects the connection with the other server 6 after receiving the search result, and outputs the received search result. The list is saved in the temporary storage of the hard disk 10. Subsequently, the search result list compression program 36 reads out the search result list, which is the download data stored in the temporary storage of the hard disk 10, compresses it, and stores the compressed data on the hard disk 10. The search result list in the temporary storage is deleted. Then, the notification and transmission server program 37
The fact that the compressed data can be downloaded at any time is displayed on the WW page. The client user sees the WWW page and is notified that the compressed data can be downloaded.

(Eighth Embodiment) FIG. 20 is a schematic view of the eighth embodiment. The data acquisition / notification device 4 transmits an applet, which is a network-loadable search agent, to the client 5, and the applet
URL of the data desired by the user of the client 5
The applet downloads the desired data from the other server 6 by designating the download destination to the data acquisition notifying device 4, and the data acquisition notifying device 4 compresses the download data and notifies the data to be saved. The client 5 downloads it. Reference numeral 43 denotes the movement of the applet at this time, and reference numeral 44 denotes
Indicates the flow of URL data, reference numeral 45 indicates the flow of download data, and reference numeral 46 indicates the flow of compressed data.

The applet is an agent which is downloaded from the server and operates on the applet virtual machine on the client side.
A process that performs client-server communication with the et operates, and realizes a remote programming method in which both work in cooperation. However, in this case, inconvenience occurs when the client suspends the connection to the Internet, so the server-side process creates a new search agent in the cooperation, and this becomes a virtual browser, and the location of the activity is made to another server. Alternatively, the required data may be downloaded from the other server to the server, compressed and stored on the server side, notified to the client, and provided to the client.

[0060]

As described above, according to the present invention, the time required for the client to receive data from the server desired by the client can be shortened and increased, and as a result, the resources can be effectively used.

[Brief description of the drawings]

FIG. 1 is a diagram showing an overall configuration of a data acquisition notification device.

FIG. 2 is a diagram showing a hardware configuration when the device in FIG. 1 is realized using a CPU 2.

FIG. 3 is a flowchart of a URL reception server program 30;

FIG. 4 URL data 40 via the Internet
It is a figure showing the flow of.

FIG. 5 is a diagram showing a display screen displayed on a display D on the client side.

FIG. 6 is a flowchart of a data reception client program 31.

FIG. 7 is a WWW page 60 via the Internet.
It is a figure showing the flow of.

FIG. 8 is a flowchart of a compression program 32;

9 is a flowchart of a notification and transmission server program 33. FIG.

FIG. 10 shows compressed data 41 via the Internet.
It is a figure showing the flow of.

FIG. 11 is a diagram showing a display screen displayed on a display D on the client side.

FIG. 12 is a flowchart of a URL and an e-mail address reception server program.

FIG. 13 is a diagram showing a display screen displayed on a display D on the client side.

FIG. 14 is a flowchart of a notification e-mail transmission server program.

FIG. 15 is a diagram showing the flow of a notification e-mail 42 via the Internet.

FIG. 16 is a flowchart of a URL reception server program by e-mail.

FIG. 17 is a flowchart of a link rewriting server program.

FIG. 18 is a flowchart of an icon replacement server program.

FIG. 19 is a diagram illustrating a hardware configuration in the case of a keyword search.

FIG. 20 is a schematic diagram showing a flow of each data in the remote programming method.

[Explanation of symbols]

REFERENCE SIGNS LIST 1 control device 10 storage device 13 transmission / reception device 23 CD-ROM 30 URL reception server program constituting data acquisition notification program 31 same data reception client program 32 same data compression program 33 same notification and transmission server program 34 data acquisition notification program The keyword receiving server program 35 The keyword search client program 36 The search result list compression program 37 The notification and transmission server program

Claims (9)

[Claims] An input unit for receiving a URL of data to be obtained; an obtaining unit for accessing the URL of the input unit to issue a request for obtaining the data and storing received data in a cache memory; And a notifying unit that enables access to the compressed data and notifies a client that the compressed data is accessible. 2. The data acquisition notifying device according to claim 1, wherein the notifying unit includes a WWW server unit that generates a hypertext in which a link to the compressed data is described and presents it to a client. A data acquisition notifying device characterized by the above-mentioned. 3. The data acquisition notifying device according to claim 1, wherein the notifying unit includes an e-mail transmitting unit for transmitting an e-mail describing a URL for accessing the compressed data to a client. A data acquisition notification device. 4. Accessing a URL provided from a client via a network to obtain required data,
A data acquisition notifying method comprising compressing data after acquiring the data, setting the compressed data in a downloadable state, and notifying the client of the state. 5. The data acquisition notifying method according to claim 4, wherein the client is notified by presenting a hypertext with a link to the compressed data. 6. The data acquisition notifying method according to claim 4, wherein the client is notified by sending an electronic mail describing a URL for accessing the compressed data to the client. Method. 7. A recording medium which records a program for causing a computer having an acquisition unit for acquiring required data by accessing a URL of data to be acquired, wherein the URL of the data to be acquired is recorded. Is received by the input unit, the acquisition unit accesses the URL of the input unit, issues a request to acquire the data, stores the received data in the cache memory, and compresses the data in the cache memory by the compression unit and stores the data in the storage device. A recording medium which stores a program for causing a computer to perform a process of storing and notifying a client that the compressed data is accessible by the notifying unit and that the compressed data is accessible. 8. A recording medium on which the program according to claim 7 is recorded, wherein the notifying process notifies a client by generating and presenting a hypertext in which a link to compressed data is described. A recording medium having recorded thereon a program. 9. A recording medium on which the program according to claim 7 is recorded, wherein the notifying process notifies the client by transmitting an electronic mail describing a URL for accessing the compressed data to the client. A recording medium on which a program is recorded.