JP2000076188A - Homepage management method and storage medium storing program for executing the method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To judge whether or not access is valid on the side of a client machine without accessing server machine and to display a fine message corresponding to a valid period from a server to the client machine. SOLUTION: The server machine 101 transfers a homepage, an access number- of-times control program 104 for counting the number of times of the access to the homepage and a message file 105 for each number of times of the access to the client machine at the access of a first time from the client machine 100 to the homepage 103. In the client machine 100, the held access number-of- times control program counts the number of times of the access to the homepage after the next time, reads a message corresponding to the number of times of the access from the receiving massage file for each number of times of the access, displays it, and if the number of times of the access exceeds the number of times set beforehand, inhibits the access to the homepage.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a homepage management method for managing homepages published on the Internet, and more particularly to a homepage management method capable of restricting access to homepages.

[0002]

2. Description of the Related Art In recent years, a world wide computer network called the "Internet" has been widely used. Along with this, an information group called "homepage" is set up on a "server" which is a computer system connected to the Internet, and various information such as product guides and personal opinions are disclosed to the whole world. Companies and individuals are increasing rapidly.

[0003] Originally, a "homepage" is an H obtained from a WWW (World Wide Web) site on the Internet.
This means the first “page” when an HTML text file described in HTML (Hyper Text Markup Language) is displayed by a predetermined browser. However, recently, the homepage has recently turned to an aggregate of a series of information such as other related image files and audio files in addition to the HTML text file described above. In addition, recently, homepages have been released for a fee.

[0004] In this case, access to the paid homepage is managed by a server machine. Only when the server machine receives an input from a "client" machine, which is a computer system connected to the server machine via the Internet, an identifier for certifying the member paying the fee, the server machine sends the home page to the client machine. To transfer the contents.

[0005] As a conventional technique relating to a pay homepage for providing the above-mentioned pay information, a technique described in, for example, JP-A-09-146824 is known.

On the other hand, recently, a technique has been proposed in which a program created by JAVA is transferred to a client machine together with a homepage, and the program is operated on the client machine.

According to these conventional techniques, when a home page is first transferred from a server machine to a client machine, a dialogue identifier for identifying the client machine is given a generation date and time to issue a dialogue identifier,
The next time the client machine accesses the server machine from the client machine, the client machine attaches the dialogue identifier, so that the server machine identifies the client machine requesting the access and determines the number of accesses from the date and time when the dialogue identifier was generated. If the expiration date has passed, information provision will not be accepted, and unauthorized information provision will be prevented.

[0008]

The prior art described above is
When a request for information provision is made by accessing a server machine from a client machine, it is possible to determine whether the request is valid or invalid for the first time. There is a problem that a communication fee is imposed on the machine.

Further, in the above-mentioned prior art, a message corresponding to the remaining expiration date of the dialogue identifier cannot be displayed on the client machine, and whether or not the user can receive the information is provided. There is a problem that it is not possible to know whether or not it is possible to receive the information.

[0010] An object of the present invention is to solve the above-mentioned problems of the prior art, and to enable a client machine to determine whether access is valid or invalid without accessing a server machine. It is an object of the present invention to provide a homepage management method which enables a detailed message to be displayed on a client machine as a deadline approaches.

[0011]

According to the present invention, there is provided a homepage management method for managing a homepage on a server machine published on a computer network, wherein the server machine sends a homepage from a client machine to the homepage. At the first access, an access count control program that counts the number of accesses to the homepage together with the homepage is transferred to the client machine, and the client machine holds the access count control program from the server machine, and the access held by the client machine. The number-of-times control program counts the number of times of access each time the home page is accessed next time, and prohibits access to the home page when the number of accesses exceeds a preset number. More is achieved.

Further, the object is that the server machine further holds a message file for each access count and transfers it to the client machine, and the client machine also holds a message file for each access count from the server machine. The access number control program held in the client machine counts the number of times of access each time the homepage is accessed after the next time,
This is achieved by reading out and displaying the message content corresponding to the access count from the message file for each access count.

[0013] Further, the object is that the server machine holds an access restriction release program, transfers the access restriction release program to the client machine, and the client machine operates the access restriction release program stored in its own machine. This is achieved by releasing the prohibition of access to the homepage.

The present invention having the above-described structure provides a program described in JAVA for determining the number of valid accesses when transferring a homepage from a server machine to a client machine, and a message storing a message corresponding to the remaining number of valid accesses. The file and the home page are transferred to the client machine together with the homepage. Thereafter, each time the client machine accesses the server machine, the number of accesses is counted, and a message corresponding to the remaining number of valid access times is displayed on the client machine, and the effective access time is displayed. When an access request to the server machine is issued more than the number of times, a message indicating that access has been invalidated can be displayed on the client machine without accessing the server machine.

[0015]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of a homepage management method according to the present invention will be described below in detail with reference to the drawings.

FIG. 1 is a block diagram showing the configuration of a system for executing a homepage management method according to an embodiment of the present invention, FIG. 2 is a diagram for explaining the contents of an access count corresponding message file, and FIG. FIG. 4 is a flowchart illustrating the processing operation, and FIG. 4 is a flowchart illustrating the processing operation of the access restriction release program. In FIG. 1, 100 is a client machine, 1
01 is a server machine, 102 is a browser, 103, 10
6 is homepage information, 104 and 107 are access number control programs, 105 and 108 are access number corresponding message files, and 109 and 110 are access restriction release programs.

A system for executing a homepage management method according to an embodiment of the present invention includes a client machine 100 and a server machine, each of which is a computer system interconnected via a computer network such as the Internet as shown in FIG. 101. The server machine 101 stores home page information 103, an access count control program 104, an access count correspondence message file 105, and an access restriction release program 109. The client machine stores a browser 102 and home page information 106, an access count control program 107, an access count correspondence message file 108, and an access restriction release program 110, which are transferred from the server machine. You.

In the embodiment of the present invention configured as described above, when the client machine 100 accesses the homepage information 103 of the server machine 101, the server machine 101 needs to manage the homepage information. In this case, the home page information 103 is transferred to the client machine 100, and the access number control program 104 and the access number corresponding message file 105 are transferred to the client machine 100. The client machine 100 stores the transferred home page information 103, the access number control program 10
4. The message file 105 corresponding to the number of accesses is stored in the homepage information 10 via the browser 102.
6. The access number control program 107 and the access number corresponding message file 108 are stored in the own machine 100.

The access number control program 104 described above.
Means that the client machine 100
Is a program described in JAVA that determines the number of valid accesses to the home page when the home page is transferred to the server. The access number correspondence message file 109 stores a message corresponding to the remaining number of valid accesses to the home page. Server machine 1 along with the homepage 103
01 to the client machine.

The access control program 107 transferred to the client machine 100 counts the number of accesses each time the client machine 100 accesses the server machine 101 thereafter, and outputs a message corresponding to the remaining number of valid accesses to the client machine 100. 10
0, and when an access request to the server machine 101 exceeds the number of valid accesses, a message indicating that access has been invalidated without accessing the server machine 101 is sent to the client machine 100.
To be displayed.

That is, when the user of the client machine 100 requests a URL for communication via the browser 102, the access number control program 107
The URL of the communication destination is obtained from the browser 102, and a message corresponding to the access count is obtained from the access count corresponding message file 108 and displayed. At this time, if the set maximum number of accesses is exceeded, the access is stopped.

The number of accesses is limited by transferring the access restriction release program 109 from the server machine 101 to the client machine 100, and
00 operates the access restriction release program 110 stored in the own machine 100, and deletes the corresponding record in the access number corresponding message file 108 to remove it.

Next, an example of the access count corresponding message file 108 will be described with reference to FIG.

Access Number Corresponding Message File 10
8, URL column 201, access frequency column 202, message sequence 203, maximum frequency column 204, as shown in FIG.
And a current count column 205. The URL column 201 stores a URL for specifying the server machine of the communication destination, and the access count column 202 stores a message displayed for each access count to the corresponding URL.
The maximum frequency column 204 stores the maximum number of accesses to the URL, and the current frequency column 205 stores the URL.
The number of times L has been accessed so far is stored. Further, a portion 206 surrounded by “%” in the message in the message sequence 203 represents a portion to be displayed by replacing with a result of performing an operation (in the illustrated example, maximum number−current number) at the time of displaying the message.

An example of the access number correspondence message file 108 shown in FIG. 2 is that the homepage information shown in FIG.
A case in which only a specific member is permitted access, and the user who intends to become a member is allowed several trials to determine whether it may be a member. This is an example, and shows an example in which the maximum number of trials is set to five. Then, as a message 203, at the time of the first access, it is displayed that the homepage of the URL is under trial, and at the time of the second to fourth access, how many times the trial period ends is displayed. Message is stored, and at the time of the fifth access, the validity count expires.
Thereafter, a message for displaying a procedure or the like when the user wants to use the service is stored. Further, as a message when the access has been performed more than five times, a message indicating that the number of valid times has been exceeded and the access is not possible is stored.

Next, the processing operation of the access count control program will be described with reference to the flow shown in FIG.

(1) First, when the user of the client machine 100 requests communication from a certain URL via the browser 102, the access number control program 107
Obtains the URL of the access destination to the browser 102 by inter-program communication, and determines whether or not there is a record corresponding to the obtained URL in the access count correspondence message file 108 (steps 301 and 30).
2).

(2) If it is determined in step 302 that the corresponding record does not exist in the access number correspondence message file 108, it is determined that access restriction is not set for the URL, and the URL is determined.
The access to L is executed (step 311).

(3) If it is determined in step 302 that the corresponding record exists in the access number correspondence message file 108, the current number 205 of the record is set to 1
It counts up (step 303).

(4) Next, the message 203 corresponding to the access count 202 corresponding to the current count of the corresponding record in the access count corresponding message file 108 is read, the message content is analyzed, and the converted character string portion is included in the message. It is determined whether there is (for example, 206 in FIG. 2) (steps 304 and 305).

(5) If it is determined in step 305 that there is a converted character string portion in the message, a message to be displayed is created by replacing that portion with the result of the operation (step 306).

(6) If the processing in step 306 is performed, the message created in step 306 is displayed. If it is determined in step 305 that the converted character string is not included in the message, the access number correspondence message file 108 is displayed. Is displayed as it is (step 307).

(7) Next, it is determined whether or not the current number exceeds the maximum number. If the current number exceeds the maximum number,
Assuming that the right to access the URL has expired, access to the target URL is stopped, and the process ends (steps 308 and 310).

(8) If it is determined in step 308 that the current number does not exceed the maximum number, a setting is made to the server machine 101 so that the transfer of the access number corresponding message file is not required, and the target URL is accessed. Then, the process ends (steps 309 and 311).

Next, the processing operation of the access restriction restriction release program 110 will be described with reference to the flow shown in FIG. This operation is to release the restriction on the number of times of access, and when the user obtains the access right after the expiration of the period of access to the URL (number of times) or after the expiration of the period, the server machine 101 transmits the URL. Client machine 1
The client computer 100 operates the access restriction release program 110 transferred to the access number 00 and deletes the corresponding record in the access number correspondence message file 108, whereby the access restriction can be released.

(1) First, a message file corresponding to the number of accesses is searched by the URL set in the access restriction release program 110, and it is determined whether or not a record corresponding to the URL is present in the message file 108 corresponding to the access number. (Steps 401 and 402).

(2) If it is determined in step 402 that the record corresponding to the URL does not exist, the process ends without performing any processing. If it is determined that the record corresponding to the URL exists, the record is deleted. Is deleted and the process is terminated (step 403).

According to the above-described embodiment of the present invention, the client machine can determine whether the access is valid or invalid without accessing the server machine. In this case, unnecessary access to the server machine can be suppressed at the time, and an extra communication fee can be prevented from being applied to the client machine.

Further, according to the embodiment of the present invention, a fine message message corresponding to the remaining number of valid accesses can be displayed on the client machine, so that the user is suddenly denied access to the server machine. It can ease the thought of being done.

Note that the access count control program, the message file for each access count, and the access restriction release program in the embodiment of the present invention are as follows.
It can be configured to be stored in a recording medium such as FD, CDROM, DVD, or the like, thereby managing a home page.

[0041]

As described above, according to the present invention, the management of the user is conventionally performed on the server machine side, and the management of the usage limitation is performed. Management can be performed, and a message corresponding to the number of accesses can be displayed.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating a configuration of a system that executes a homepage management method according to an embodiment of the present invention.

FIG. 2 is a diagram illustrating the contents of an access count corresponding message file.

FIG. 3 is a flowchart illustrating a processing operation of an access number control program.

FIG. 4 is a flowchart illustrating a processing operation of an access restriction release program.

[Explanation of symbols]

 Reference Signs List 100 client machine 101 server machine 102 browser 103, 106 homepage information 104, 107 access count control program 105, 108 access count correspondence message file 109, 110 access restriction release program

Claims (4)

[Claims] 1. A homepage management method for managing a homepage on a server machine published on a computer network, wherein the server machine accesses the homepage for the first time from a client machine.
An access number control program for counting the number of accesses to the home page together with the home page is transferred to the client machine.The client machine holds the access number control program from the server machine, and the access number control program held by the client machine includes: A homepage management method comprising: counting the number of accesses each time the homepage is accessed next time; and prohibiting access to the homepage when the number of accesses exceeds a preset number. 2. A homepage management method for managing a homepage on a server machine published on a computer network, wherein the server machine accesses the homepage for the first time from a client machine.
An access count control program for counting the number of accesses to the homepage together with the homepage, and a message file for each access count are transferred to the client machine, and the client machine transmits the access count control program from the server machine and the message file for each access count. The access number control program held in the client machine counts the number of accesses each time the homepage is accessed next time, and reads the message content corresponding to the number of accesses from the message file for each access number. And displaying the web page when the number of accesses exceeds a preset number of times, and prohibiting access to the home page. 3. The server machine retains an access restriction release program, transfers the access restriction release program to a client machine, and the client machine operates the access restriction release program stored in its own machine to execute the access restriction release program. 3. The homepage management method according to claim 1, wherein the prohibition of access to the homepage is released. 4. An access count control program for executing the homepage management method according to claim 1, 2 or 3, a message file for each access count, and an access restriction release program are stored. recoding media.