JP6015051B2 - Groupware system, cache method and cache program in groupware system - Google Patents

Description

  The present invention relates to a groupware system used by a plurality of users, a cache method in the groupware system, and a cache program.

  In a groupware system (hereinafter also referred to as “groupware”), which is software for sharing information utilizing a computer network in an organization such as a company, a user is generally a user terminal (hereinafter referred to as a “client terminal”). After logging in to the groupware system, the user confirms the presence or absence of new addition information or change information (hereinafter also referred to as “new arrival information”) on the server, and the necessary information. Is downloaded from the server to the client terminal by the user himself / herself.

  Furthermore, in other groupware, shared information such as documents is frequently added / changed, so what is accessed once by the user is saved from the server to the client terminal side (hereinafter referred to as “cache”). There is also a method that has been adopted.

  A technique for improving the efficiency of the confirmation process of newly arrived information for each user is also described in Patent Document 1. Patent Document 1 discloses a system that includes a normal mobile terminal and an information collection server instead of groupware, and the information collection server receives new arrival information from a plurality of external servers at certain time intervals according to setting information for each user. Collect and accumulate.

JP 2006-344073 A

  In the groupware using the cache method described above, when a document that has been accessed once is accessed from the second time onward, it is only necessary to access the document that has been cached on the client terminal side. The time (response time) from when the message is displayed to when the text is displayed can be improved. However, general groupware often accesses new arrival information such as new mail and newly registered documents, but such new arrival information is naturally not cached on the client terminal side, so it is necessary to go to the server. There is. That is, in such a case, there is a problem that it takes time to transfer newly arrived information data from the server to the client terminal, and a reduction in response time cannot be expected.

  In addition, the above-mentioned Patent Document 1 does not describe anything about providing the cache information on the mobile terminal side, and after the user selects the new arrival information necessary on the mobile terminal, the information Is downloaded from the information collection server to the mobile terminal. Therefore, the technique described in Patent Document 1 also has a problem that the response time until the user can obtain necessary information cannot be expected.

  An object of the present invention is to provide a groupware system, a cache method, and a program that can solve the various problems described above.

The groupware system of the present invention comprises at least one client terminal and a server connected to the client terminal,
The server
Database means for registering multiple files;
Cache target information means for storing cache target information including attribute information having a file identifier for identifying the file and a flag indicating whether or not the file is registered in the client terminal;
When there is a user logged out from the groupware system at the time when a new file is registered in the database means or when the file registered in the database means is updated The cache target information corresponding to the user has the file identifier that identifies the new file or the file that has been updated, and the flag that indicates that the file is not registered in the client terminal. A user cache creation means for adding attribute information, and
The client terminal is
When the cache unit and the user log in to the groupware system, the cache target information corresponding to the user is acquired from the cache target information unit, and the attribute information included in the acquired cache target information A user cache unit that downloads the file from the database unit and registers the file in the cache unit when the flag indicates that the file specified by the file identifier is not registered in the client terminal; Consists of

The cache method of the present invention is a groupware system comprising at least one client terminal and a server connected to the client terminal.
A registration step of registering the file in the database means of the server;
Cache target information including attribute information having a file identifier for specifying the file and a flag indicating whether the file is registered in the client terminal is stored in the cache target information means of the server for each user. A cache target information storage step;
When there is a user logged out from the groupware system at the time when a new file is registered in the database means or when the file registered in the database means is updated The cache target information corresponding to the user has the file identifier that identifies the new file or the file that has been updated, and the flag that indicates that the file is not registered in the client terminal. A user cache creation step for adding attribute information;
When the user logs in to the groupware system, the cache target information corresponding to the user is acquired from the cache target information means, and the file in the attribute information included in the acquired cache target information A user cache registration step of downloading the file from the database unit and registering the file in the cache unit of the client terminal when the flag indicates that the file specified by the identifier is not registered in the client terminal Includes and.

The cache program of the present invention is a groupware system in which a plurality of users use beta base means for registering a plurality of files.
Cache target information storage for storing cache target information including attribute information having a file identifier for specifying a file and a flag indicating whether or not the file is registered in the cache unit in the cache target information storage unit for each user Processing,
When the user logs in to the groupware system, the cache target information updated by reflecting the registration or update of the file in the database unit is received from the outside and stored in the cache target information storage unit, and the cache When the flag indicates that the file specified by the file identifier in the attribute information included in the target information is not registered in the cache unit, the file is downloaded from the database unit, Let the computer execute the registration process to register in the cache.

  As described above, the present invention has an effect that the groupware can achieve a reduction in response time of file access as viewed from the user side.

FIG. 1 is a block diagram of a first embodiment of the present invention. FIG. 2 is a diagram illustrating an example of cache target information according to the first embodiment. FIG. 3 is a flowchart illustrating an operation at the time of new arrival information registration of the server in the first embodiment. FIG. 4 is a flowchart showing an operation at the time of login to the groupware by the user of the client terminal in the first embodiment. FIG. 5 is a flowchart showing an operation at the time of document access by a groupware user in the first embodiment. FIG. 6 is a block diagram of the second exemplary embodiment of the present invention. FIG. 7 is a flowchart showing an operation when the user uses the client terminal in the second embodiment.

  Next, embodiments of the present invention will be described in detail with reference to the drawings.

[First Embodiment]
FIG. 1 is a block diagram showing a first embodiment of the present invention.

  Referring to FIG. 1, the present embodiment includes a plurality of client terminals 100 and a server 200.

  Each client terminal 100 includes a user cache unit 110, a groupware client function unit 120, an input / output unit 130, and an interface unit 140. The user cache unit 110 includes a cache information storage area 150 and a cache target information storage area 160.

  The server 200 includes a new arrival information confirmation unit 210, a user cache creation unit 220, a cache target information unit 230, a cache provision unit 240, a database unit 250, a user management unit 260, a download request reception unit 270, An interface unit 280.

  Note that FIG. 1 shows only components related to the present invention out of the entire groupware configuration composed of a plurality of client terminals 100 and servers 200.

  Next, the configuration and operation of the client terminal 100 and the server 200 will be briefly described.

  The database unit 250 is a data storage area in which a plurality of users can share various data such as documents and emails.

  The cache target information section 230 stores a list of file attribute information registered or updated in the database section 250 (hereinafter also referred to as “cache target information”), and is created for each groupware user. Retained. Therefore, the content of the attribute information held in the cache target information unit 230 differs for each user.

  FIG. 2 shows an example of cache target information of a user A stored in the cache target information unit 230. Referring to FIG. 2, the cache target information includes a plurality of attribute information, and each attribute information includes a document file ID, a document file name, and a cached flag.

  For example, looking at the second line, “fileA” is the file ID of the document, “Notice of health check” is the file name of the document, and “1” is the cached flag. When the cached flag is “1”, the file corresponding to the attribute information of the line is already downloaded to the client terminal used by the user A and stored in the cache information storage area 150 described later. In the case of “0”, the file corresponding to the attribute information of the line is not yet downloaded to the user A's client terminal.

  Hereinafter, the state where the file is downloaded to the client terminal and the cached flag is “1” is also referred to as “cached”, and the state where the cached flag is not downloaded to the client terminal and the cached flag is “0” is also referred to as “uncached”. say.

  The cache target information storage area 160 is an area for downloading and holding cache target information corresponding to a user who has logged in to the groupware from the cache target information unit 230.

  The cache information storage area 150 downloads and holds uncached files (files whose cached flag is “0”) among a plurality of attribute information in the cache target information held in the cache target information storage area 160. It is an area.

  The user cache unit 110 receives the cache target information in the cache target information unit 230 created for each user and the uncached file among the attribute information included in the cache target information from the cache providing unit 240 described later. Received and stored in the cache target information storage area 160 and the cache information storage area 150, respectively. Further, the user cache unit 110 checks whether or not the file specified by the user exists in the cache information storage area 150 in response to a request from the groupware client function unit 120 described later. The file is passed to the groupware client function unit 120.

  The groupware client function unit 120 has a function provided on the client side in general groupware, and further has a function of notifying user authentication information (user ID, user password) to the user cache unit 110. Further, whether or not the file specified by the user exists in the cache information storage area 150 is confirmed by the user cache unit 110. If it exists, the user receives the file from the user cache unit 110, and If it does not exist, the file is downloaded from the database unit 250 to the client terminal 100 and presented to the user in the same manner as general groupware.

  The input / output unit 130 has a function of receiving an operation from a groupware user and notifying the user of the operation result and information.

  The interface unit 140 and the interface unit 280 are used to exchange data between the client terminal 100 and the server 200. The interface unit 140 also exchanges data between the input / output unit 130 and the groupware client function unit 120.

  The new arrival information confirmation unit 210 monitors the registration process of a new file in the database unit 250 and the update process of an existing file, and if these processes are performed, the user cache creation unit 220 described later (that is, that is, "New arrival information registration") is notified, and attribute information (file ID and file name) of the file is passed.

  The user cache creation unit 220 receives a notification of new arrival information registration from the new arrival information confirmation unit 210 described above, and determines the current status of the user from the user information of the groupware managed by the user management unit 260 described later. The attribute information of the file is added to the cache target information in the cache target information unit 230 that is acquired and corresponding to the user. When the attribute information already exists in the cache target information, the cached flag of the attribute information is updated to “0”. When the user is currently logged in, the above-described cache target information is transferred to the user cache unit 110 on the client terminal 100 via the cache providing unit 240.

  The user management unit 260 manages the login status of the user to the groupware, and provides the current user status in response to the request from the user cache creation unit 220 described above.

  In response to the request from the user cache unit 110 described above, the cache providing unit 240 stores the cache target information in the cache target information unit 230 corresponding to the specified user, or the specified file acquired from the database unit 250. The data is passed to the cache unit 110. Conversely, in response to a request from the above-described user cache creation unit 220, specified cache target information is passed to the user cache unit 110.

  The download request receiving unit 270 acquires the file requested by the groupware client function unit 120 from the database unit 250 and passes it to the groupware client function unit 120.

  While the configuration and operation of each component have been briefly described above with reference to FIG. 1, some or all of the client terminal 100 and server 200 shown in FIG. 1 are a general computer system that operates under program control. It may be realized, or may be realized by dedicated hardware.

  Next, the operation of this embodiment will be described in detail with reference to the flowcharts of FIGS.

  FIG. 3 is a flowchart showing an outline of the operation at the time of new arrival information registration in the server 200.

  Referring to FIG. 3, first, it is assumed that a file is registered in the database unit 250 by a certain user, or an already registered file is updated (step S301).

  The new arrival information checking unit 210 monitors file registration, update, and deletion events in the database unit 250, and attribute information (file ID, file name) of a file registered or updated when a file registration or update event occurs Etc.) to the user cache creation unit 220 (step S302).

  The user cache creation unit 220 receives the notification from the new arrival information confirmation unit 210 and acquires the current status of all users from the user information managed by the user management unit 260. Then, the above-described registered or updated file attribute information is added to the cache target information in the cache target information section 230 created for each user. At this time, the attribute information also includes a cached flag “0”. If the same information as the attribute information of the registered or updated file already exists in the cache target information, the cached flag of the attribute information is updated to “0” (step S303).

  Next, when the user is currently logged in to the groupware, the following step S305 is executed (step S304). That is, the user cache creation unit 220 sends the above-described user cache unit 110 operating on the client terminal 100 used by the user to the above-described unit via the cache providing unit 240, the interface unit 280, and the interface unit 140. Pass cache target information. Then, the user cache unit 110 overwrites the cache target information already existing in the cache target information storage area 160 with the received cache target information (step S305).

  In this way, the user cache creation unit 220 repeats the processing from step S303 to step S305 described above for all users (step S306).

  As described above, the attribute information of the file registered or updated in the database unit 250 is added to the cache target information of each user.

  FIG. 4 is a flowchart showing an outline of the operation when the user of the client terminal 100 logs in to the groupware.

  First, it is assumed that the user has already logged in to the client terminal.

  As shown in FIG. 4, when the user subsequently logs in to the groupware, the groupware client function unit 120 notifies the user cache unit 110 of the fact and the user authentication information (user ID, user password). To do. (Step S401).

  Next, the user cache unit 110 clears the cache target information storage area 160, passes the user authentication information to the cache providing unit 240 via the interface unit 140 and the interface unit 280, and creates the information for the user. The cache target information in the cache target information unit 230 is requested. The cache providing unit 240 passes the cache target information for the user to the user cache unit 110 via the interface unit 280 and the interface unit 140 based on the passed authentication information. The user cache unit 110 overwrites the cache target information already existing in the cache target information storage area 160 with the cache target information received from the cache providing unit 240 (step S402).

  As described above, the attribute information of the file registered or updated in the database unit 250 after the time when the user logged out last time is stored in the cache target information storage area 160.

  Then, the user cache unit 110 confirms the contents of the cached flag included in each attribute information in the cache target information stored in the cache target information storage area 160 (step S403).

  When there is attribute information whose cached flag is “0” (not cached), the user cache unit 110 downloads the corresponding file through the interface unit 140 and the interface unit 280 based on the file ID included in the attribute information. Request to the cache providing unit 240.

  The cache providing unit 240 acquires the file requested from the user cache unit 110 from the database unit 250, passes the file to the user cache unit 110 via the interface unit 280 and the interface unit 140, and cache target information for the user. The cached flag of the attribute information corresponding to the file included in the cache target information in the unit 230 is updated to “1”.

  Then, the user cache unit 110 saves the file received from the cache providing unit 240 in the cache information storage area 150 and sets the cached flag of the attribute information corresponding to the file held in the cache target information storage area 160. It is updated to “1” (step S404).

  The user cache unit 110 performs processing in the above-described step S404 on a file whose cached flag included in the attribute information in the cache target information stored in the cache target information storage area 160 is “0” (uncached file). It repeats until it downloads all (step S405).

  If the cached flag of all the attribute information is “1” (cached) in step S403 described above, the user cache unit 110 ends the process.

  As described above, the cache information storage area 150 of the client terminal 100 stores files registered or updated in the database unit 250 after the time when the user logged out last time.

  FIG. 5 is a flowchart showing an outline of the operation of the client terminal 100 when the user accesses the file.

  Referring to FIG. 5, first, when a user accesses a file via the input / output unit 130 (step S501), the groupware client function unit 120 determines whether or not the file exists in the cache information storage area 150. The user cache unit 110 is inquired (step S502).

  The user cache unit 110 confirms the contents of the cached flag included in the attribute information stored in the cache target information storage area 160 based on the file ID of the file, and the cached flag of the attribute information corresponding to the file is determined. In the case of “1” (cached), the file is acquired from the cache information storage area 150 and transferred to the groupware client function unit 120 together with a response that the cache has been completed. If the cached flag is “0” (cache not yet), a response indicating that the cache is not cached is returned to the groupware client function unit 120 (step S503).

  When the response from the above-described user cache unit 110 is already cached, the groupware client function unit 120 displays the transferred file to the user via the input / output unit 130 (step S505).

  With the above processing, when the file has been cached in the client terminal 100, it is not necessary to download from the database unit 250, and the time for data transfer processing can be omitted. It can be shortened.

  Next, when the response from the user cache unit 110 is not cached in step S503 described above, the groupware client function unit 120 downloads the file via the interface unit 140 and the interface unit 280, and the download request receiving unit 270. To request.

  Then, the download request receiving unit 270 acquires the file requested from the groupware client function unit 120 from the database unit 250 and passes the file to the groupware client function unit 120 via the interface unit 280 and the interface unit 140 (step S504).

  Next, the groupware client function unit 120 displays the file passed from the download request receiving unit 270 to the user via the input / output unit 130 (step S505).

  The reason why the file that the user wants to access is not cached as described above is that the file download process at the time of user login described with reference to the flowchart of FIG. This is because the user may request access to the file earlier than the timing when the download process is completed.

  As described above, the present embodiment has an effect that the response time from when a user accesses a file on the client terminal 100 to when the file is displayed can be shortened.

  The reason is that the attribute information corresponding to the file registered or updated in the database unit 250 on the server 200 side after the user logs out is held, and the client terminal is in accordance with the attribute information when the user logs in next time. This is because files that do not exist on the 100 side can be automatically downloaded from the server 200 and saved.

[Second Embodiment]
Next, a second embodiment of the present invention will be described.

  In the first embodiment, the user cache unit 110 downloads an uncached file from the database unit 250 and stores it in the cache information storage area 150 when the user logs in to the groupware. However, when a user accesses a new file immediately after logging in to the groupware, the new file may not be saved in the cache information storage area 150 yet. In that case, the response time cannot be shortened.

  Therefore, in the second embodiment, after the user logs in to the client terminal 100, before the user logs in to the groupware, a file that has not been cached is downloaded and stored as background processing of the client terminal 100. Thus, the response time in the above situation is shortened.

  Hereinafter, the present embodiment will be described in detail with reference to the drawings.

  In the following description, description of components and operations that are the same as those in the first embodiment will be omitted.

  FIG. 6 is a block diagram showing this embodiment.

  Referring to FIG. 6, the client terminal 100 according to this embodiment includes a groupware authentication information unit 170 that is not present in the first embodiment.

  The groupware authentication information unit 170 stores authentication information (user ID and user password) used when a user logs in to the groupware, and is a user-specific storage area provided in the client terminal 100. Retained.

  More detailed operations of the client terminal 100 and the server 200 of the second embodiment will be described with reference to the flowchart of FIG.

  FIG. 7 is a flowchart showing the operation of the client terminal 100 when the user uses the client terminal.

  Here, in this embodiment, the user cache unit 110 is configured to operate even in the background of the client terminal. Referring to FIG. 7, when the user first logs in to the client terminal 100, the user cache unit 110 is The operation is started in the background (step S701).

  Next, after clearing the cache target information storage area 160, the user cache unit 110 acquires the user authentication information from the groupware authentication information unit 170, and provides the cache via the interface unit 140 and the interface unit 280. The authentication information is passed to the unit 240 and the cache target information in the cache target information unit 230 created for the user is requested. The cache providing unit 240 acquires the cache target information for the user from the cache target information unit 230 based on the passed authentication information, and passes it to the user cache unit 110 via the interface unit 280 and the interface unit 140. Then, the user cache unit 110 overwrites the cache target information already existing in the cache target information storage area 160 with the cache target information received from the cache providing unit 240 (step S702).

  As described above, the attribute information of the file registered or updated in the database unit 250 after the previous logout time from the groupware by the user is stored in the cache target information storage area 160.

  The user cache unit 110 confirms the contents of the cached flag included in each attribute information in the cache target information stored in the cache target information storage area 160 (step S703).

  When there is attribute information whose cached flag is “0” (not cached), the user cache unit 110 downloads the corresponding file through the interface unit 140 and the interface unit 280 based on the file ID included in the attribute information. Request to the cache providing unit 240.

  The cache providing unit 240 acquires the file requested from the user cache unit 110 from the database unit 250, passes the file to the user cache unit 110 via the interface unit 280 and the interface unit 140, and cache target information for the user. The cached flag of the attribute information corresponding to the file included in the cache target information in the unit 230 is updated to “1”.

  Then, the user cache unit 110 saves the file received from the cache providing unit 240 in the cache information storage area 150 and sets the cached flag of the attribute information corresponding to the file held in the cache target information storage area 160. It is updated to “1” (step S704).

  The user cache unit 110 performs processing in step S704 described above on a file whose cached flag included in the attribute information in the cache target information stored in the cache target information storage area 160 is “0” (uncached file). It repeats until it downloads all (step S705).

  Next, the user cache unit 110 waits for a certain period of time (step S706), returns to step S702, and repeatedly executes the subsequent steps. Similarly, when all the cached flags are “1” (cached) in step S703 described above, the process waits for a certain period of time, returns to step S702, and repeats the subsequent steps.

  As described above, the file registered or updated in the database unit 250 after the time when the user last logged out from the groupware was stored in the cache information storage area 150 before the user logged in to the groupware. become.

  Note that if the user logs in to the groupware while the process shown in FIG. 7 is being executed, the user cache unit 110 interrupts the operation in FIG. 7 and logs in to the groupware in FIG. The process shown by the flowchart which shows this operation | movement is performed.

  As described above, the present embodiment has an effect that the response time until the file is displayed can be shortened no matter which document is accessed immediately after the user logs into the groupware. .

  The reason is that when the user logs in to the client terminal 100 before logging in to the groupware, the user cache unit 110 operates as a background process, and files that do not exist on the client terminal 100 side are automatically transferred to the server 200 side. It is because it can be downloaded and saved from.

DESCRIPTION OF SYMBOLS 100 Client terminal 110 User cache part 120 Groupware client function part 130 Input / output part 140 Interface part 150 Cache information storage area 160 Cache object information storage area 170 Groupware authentication information part 200 Server 210 New arrival information confirmation part 220 User cache creation part 230 Cache target information section 240 Cache providing section 250 Database section 260 User management section 270 Download request receiving section

Claims (10)

In a groupware system comprising at least one client terminal and a server connected to the client terminal,
The server
Database means for registering multiple files;
Cache target information means for storing cache target information including attribute information having a file identifier for identifying the file and a flag indicating whether or not the file is registered in the client terminal;
When there is a user logged out from the groupware system at the time when a new file is registered in the database means or when the file registered in the database means is updated The cache target information corresponding to the user has the file identifier that identifies the new file or the file that has been updated, and the flag that indicates that the file is not registered in the client terminal. A user cache creation means for adding attribute information, and
The client terminal is
When the cache unit and the user log in to the groupware system, the cache target information corresponding to the user is acquired from the cache target information unit, and the attribute information included in the acquired cache target information A user cache unit that downloads the file from the database unit and registers the file in the cache unit when the flag indicates that the file specified by the file identifier is not registered in the client terminal; A groupware system characterized by including: In a groupware system in which multiple users use database means for registering multiple files,
Caching means;
Cache target information storage means for storing cache target information including attribute information having a file identifier for identifying a file and a flag indicating whether or not the file is registered in the cache means;
When the user logs in to the groupware system, the cache target information updated by reflecting the registration or update of the file in the database unit is received from the outside and stored in the cache target information storage unit, and the cache When the flag indicates that the file specified by the file identifier in the attribute information included in the target information is not registered in the cache unit, the file is downloaded from the database unit, A client terminal in a groupware system, comprising: a user cache unit registered in the cache unit. Database means for registering a plurality of files used by a plurality of users in a groupware system;
Cache target information means for storing cache target information including attribute information having a file identifier for identifying the file and a flag indicating whether the file is registered in the client terminal;
When there is a user logged out from the groupware system at the time when a new file is registered in the database means or when the file registered in the database means is updated The cache target information corresponding to the user has the file identifier that identifies the new file or the file that has been updated, and the flag that indicates that the file is not registered in the client terminal. User cache creation means for adding attribute information;
Wherein when the user logs in to the groupware system is composed of a providing means for providing the cached information corresponding to the user on the client terminal used by the user,
When the flag indicates that the file specified by the file identifier in the attribute information included in the cache target information is not registered in the client terminal, the file is downloaded from the database unit. A server in a groupware system connected to the client terminal . In a groupware system comprising at least one client terminal and a server connected to the client terminal,
The server
Database means for registering multiple files;
Cache target information means for storing cache target information including attribute information having a file identifier for identifying the file and a flag indicating whether or not the file is registered in the client terminal;
When there is a user logged out from the groupware system at the time when a new file is registered in the database means or when the file registered in the database means is updated The cache target information corresponding to the user has the file identifier that identifies the new file or the file that has been updated, and the flag that indicates that the file is not registered in the client terminal. A user cache creation means for adding attribute information, and
The client terminal is
Caching means;
Groupware authentication information used by the user to log in to the groupware system at predetermined intervals during a period in which the user logs in to the client terminal and logs out from the groupware system. The cache target information corresponding to the user is acquired from the cache target information means, and the file specified by the file identifier in the attribute information included in the acquired cache target information is registered in the client terminal. A groupware system, comprising: a user cache unit that downloads the file from the database unit and registers the file in the cache unit when the flag indicates that the file is not stored. When the user logs in to the groupware system and the file in the database means is updated, the attribute information included in the cache target information corresponding to the user is updated. Means for updating the flag included in the attribute information to indicate that the file is not registered in the client terminal when there is the attribute information including an identifier for identifying the file that has been The groupware system according to claim 1 or 4, characterized in that: In a groupware system comprising at least one client terminal and a server connected to the client terminal,
A registration step of registering the file in the database means of the server;
Cache target information including attribute information having a file identifier for specifying the file and a flag indicating whether the file is registered in the client terminal is stored in the cache target information means of the server for each user. A cache target information storage step;
When there is a user logged out from the groupware system at the time when a new file is registered in the database means or when the file registered in the database means is updated The cache target information corresponding to the user has the file identifier that identifies the new file or the file that has been updated, and the flag that indicates that the file is not registered in the client terminal. A user cache creation step for adding attribute information;
When the user logs in to the groupware system, the cache target information corresponding to the user is acquired from the cache target information means, and the file in the attribute information included in the acquired cache target information A user cache registration step of downloading the file from the database unit and registering the file in the cache unit of the client terminal when the flag indicates that the file specified by the identifier is not registered in the client terminal A cache method in a groupware system, comprising: In a groupware system comprising at least one client terminal and a server connected to the client terminal,
A registration step of registering the file in the database means of the server;
Cache target information including attribute information having a file identifier for specifying the file and a flag indicating whether the file is registered in the client terminal is stored in the cache target information means of the server for each user. A cache target information storage step;
When there is a user logged out from the groupware system at the time when a new file is registered in the database means or when the file registered in the database means is updated The cache target information corresponding to the user has the file identifier that identifies the new file or the file that has been updated, and the flag that indicates that the file is not registered in the client terminal. A user cache creation step for adding attribute information;
Groupware authentication information used by the user to log in to the groupware system at predetermined intervals during a period in which the user logs in to the client terminal and logs out from the groupware system. The cache target information corresponding to the user is acquired from the cache target information means, and the file specified by the file identifier in the attribute information included in the acquired cache target information is registered in the client terminal. A cache in the groupware system comprising: a user cache registration step of downloading the file from the database means and registering the file in the cache means of the client terminal when the flag indicates that the file is not present Direction Law. When the user logs in to the groupware system and the file in the database means is updated, the attribute information included in the cache target information corresponding to the user is updated. An update step of updating the flag included in the attribute information to indicate that the file is not registered in the client terminal if there is the attribute information including an identifier for identifying the file 8. The cache method according to claim 6 or 7, wherein: In a groupware system in which multiple users use database means for registering multiple files,
Cache target information storage for storing cache target information including attribute information having a file identifier for specifying a file and a flag indicating whether or not the file is registered in the cache unit in the cache target information storage unit for each user Processing,
When the user logs in to the groupware system, the cache target information updated by reflecting the registration or update of the file in the database unit is received from the outside and stored in the cache target information storage unit, and the cache When the flag indicates that the file specified by the file identifier in the attribute information included in the target information is not registered in the cache unit, the file is downloaded from the database unit, A cache program for causing a computer to execute registration processing registered in a cache means.





In groupware system,
A registration process for registering the file in the database means;
Cache target information storage for storing cache target information including attribute information having a file identifier for identifying the file and a flag indicating whether or not the file is registered in the client terminal in a cache target information unit for each user Processing,
When there is a user logged out from the groupware system at the time when a new file is registered in the database means or when the file registered in the database means is updated The cache target information corresponding to the user has the file identifier that identifies the new file or the file that has been updated, and the flag that indicates that the file is not registered in the client terminal. User cache creation processing to add attribute information,
When the user logs in to groupware, the computer causes the client terminal used by the user to execute the providing process of providing the cache target information corresponding to the user.

Images