JP2007316846A - Information processing terminal, method for sharing context information, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To use context information even in condition of being not able to connect to the management server of the context information. <P>SOLUTION: A user client 20 is provided with: an UI part 21; a processing part 22; a communication part 23; and a storage part 24. In acquiring context information as dynamically changing information relating to a document from a context server, the UI part 21 displays an icon showing the context server, and detects an operation for the icon, and the communication part 23 requests the transmission of the context information to the context server, and receives the transmitted context information, and the processing part 22 stores the context information as cache information 26 in the storage part 24. Also, the processing part 22 generates a cache management file 25 for performing access to the cache information 26, and stores it in the storage part 24, and in sharing the cache information 26, the processing part 22 transmits the cache management file 25 to another user client. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to an information processing terminal that uses context information, which is dynamically changing information about an electronic document.

In recent years, document management systems that centrally manage electronic documents (hereinafter simply referred to as “documents”) using a server computer (hereinafter referred to as “servers”) have been widely used. In such a document management system, a copy of a document managed by a server is often held by a client computer (hereinafter referred to as “client”) in order to efficiently perform an editing operation on the document. However, if a document managed by the server is frequently revised, the document may be changed by the server after holding a copy of the document in the client. In such a case, working with an old document held in the client will hinder business.
Therefore, a system has been proposed that always manages the latest version of a document by managing the version information of the document on the server and inquiring the version information etc. to the server when using the document on the client ( For example, see Patent Document 1).

Japanese Patent Laid-Open No. 2004-110682

Nowadays, portable devices such as notebook personal computers, PDAs (Personal Digital Assistants), and mobile phones are widely used as information processing terminals that hold document copies. Such portable devices are convenient in that they are not subject to restrictions on where the documents are used. On the other hand, there are many situations where it is not possible to connect to a management server for version information, etc., at a location where a document is to be opened. For example, when a laptop computer is taken outside the company, it is generally not possible to connect to a management server in the company. Even within the same company, it may be impossible to connect to the management server of its own department from different departments due to the network configuration and security settings.
In Patent Document 1, it is not considered that a document cannot be connected to a server that manages version information when a document is used by a client. Accordingly, further improvements have been desired in this regard.

The present invention has been made to solve the technical problems as described above, and an object thereof is to make it possible to use context information even in a situation where it is not possible to connect to a context information management server. It is in.
Another object of the present invention is to enable sharing of context information among a plurality of clients in an environment where connection to a context information management server is not possible.
Furthermore, another object of the present invention is to enable the use and sharing of context information in a situation where it is not possible to connect to the context information management server by a simple operation.

  For this purpose, in the present invention, the context information in the server is collectively cached by a simple operation while connected to the network. That is, the information processing terminal according to the present invention obtains and uses context information from a server that manages context information that is dynamically changing information about a document, and displays an object representing the server. And a communication means for receiving context information from the server in response to a user operation relating to the object, and a storage means for storing the context information received by the communication means.

  In the present invention, the cached contents can be used as a temporary context server, and the cache contents can be shared with other information processing terminals in the same network. In that case, the communication means, in response to an instruction to share the context information stored in the storage means with another information processing terminal, provides a management file for referencing the context information to the other information processing terminal. Send to.

  Furthermore, in the present invention, a server other than the cached context information management server can be used as an alternative server. In that case, the display means displays other objects representing other servers other than the management server, and the communication means displays the context information stored in the storage means in response to other user operations related to the other objects. The storage means stores the management file for referring to the context information transmitted to the other server.

  The present invention can also be understood as an information processing terminal that uses context information cached by another information processing terminal. In this case, the information processing terminal of the present invention is an information processing terminal that acquires and uses context information, which is dynamically changing information about a document, and a storage unit that stores a management file for referring to the context information. And communication means for transmitting a reference request for context information stored in another server other than the management server or an information processing terminal based on the management file when connection to the context information management server is not possible Can be grasped as.

  Furthermore, the present invention can also be understood as a method for sharing context information. In that case, the method of the present invention is a method in which the information processing terminal shares context information, which is dynamically changing information about a document, with another information processing terminal. A step of caching the context information from a server to be managed, a step of an information processing terminal generating a management file for referring to the cached context information, and an information processing terminal storing the generated management file with other information Transmitting to the processing terminal.

  On the other hand, the present invention can also be understood as a program for causing an information processing terminal that uses context information, which is dynamically changing information about a document, to realize a predetermined function. In that case, the first program of the present invention realizes a function of acquiring the context information from a server that manages the context information and a function of caching the acquired context information in accordance with a user instruction. Is. In addition, the second program of the present invention has a function of identifying other servers or information processing terminals that cache the context information other than the context information management server, and the specified other servers or information processing terminals. And a function of transmitting a reference request for cached context information.

  According to the present invention, it is possible to use dynamically changing information about a document even in a situation where it is not possible to connect to a management server for dynamically changing information about the document.

The best mode for carrying out the present invention (hereinafter referred to as “embodiment”) will be described below in detail with reference to the accompanying drawings.
FIG. 1 shows a configuration of a computer system which is a premise of the present embodiment.
As shown in the figure, in this computer system, a provider client 10, a user client 20, a document server 30, and a context server 40 are connected via a LAN (Local Area Network) 90. Although only one provider client 10, user client 20, document server 30, and context server 40 are shown in the drawing, a plurality of providers may be provided.

Among these, the provider client 10 is a client terminal used by a user (document provider) who creates or revises a document, and is realized by, for example, a general-purpose personal computer (PC).
The user client 20 is a client terminal used by a user (document user) who refers to or prints a document created or revised by a document provider. For example, the user client 20 is a general-purpose personal computer ( PC).

Further, the document server 30 centrally manages documents created or revised by a document provider and referenced or printed by a document user, and is realized by a general-purpose server computer.
The context server 40 manages dynamically changing information (hereinafter referred to as “context information”) related to documents in the document server 30 and is realized by a general-purpose server computer. Here, the context information is, for example, whether there is a newer version of a document in the same series as the document, validity / invalidity of the document or the same series of documents, comments or messages added to the document, etc. Ancillary information. Alternatively, the context information of a document may include association information with another document that is referred to or cited by the document, and document group information constituting a document group including the document. That is, various information accompanying the document that is useful for the utilization of the document can be grasped as context information.

  By the way, in this computer system, a document user holds and uses a copy of a document managed by the document server 30 in the user client 20. In that case, information for accessing the context information of the document is added to the document held in the user client 20. For example, it is the identification information (server ID) of the context server 40 that manages the context information, and the identification information (context ID) of the context information in the context server 40. Thereby, when the user client 20 opens a document, it is possible to inquire the context server 40 and refer to the context information of the document.

Next, the functional configuration of the user client 20 will be described in detail.
FIG. 2 is a block diagram showing a functional configuration of the user client 20.
As illustrated, the user client 20 includes a UI unit 21, a processing unit 22, a communication unit 23, and a storage unit 24. The storage unit 24 stores a cache management file 25 and cache information 26 by processing described later.

Among these, the UI unit 21 displays an icon or the like on a display device (not shown), or detects an operation or the like on the icon.
The processing unit 22 performs a predetermined process based on information from the UI unit 21 and the communication unit 23. As the processing performed here, for example, there is processing for receiving operation information for an icon from the UI unit 21 and requesting the context server 40 specified by the icon to transmit context information. There is also a process of receiving context information from the communication unit 23 and storing it in the storage unit 24.

Further, the communication unit 23 transmits and receives information to and from the context server 40 and other user clients 20.
The storage unit 24 stores various types of information, and such information includes the cache management file 25 and the cache information 26 as described above. Here, the cache information 26 is information obtained by caching the context information acquired from the context server 40. The cache management file 25 is a management file used when the cache information 26 is shared with other user clients 20. The cache management file 25 will be described in detail later.

These functions are realized by cooperation between software and hardware resources. That is, the UI unit 21, the processing unit 22, and the communication unit 23 are realized by a CPU (not shown) of the user client 20 reading a program that realizes these functions from, for example, a magnetic disk into the main memory.
The storage unit 24 can be realized by using various storage media such as a semiconductor memory and a magnetic disk.

Next, the functional configuration of the context server 40 will be described in detail.
FIG. 3 is a block diagram showing a functional configuration of the context server 40.
As illustrated, the context server 40 includes a UI unit 41, a processing unit 42, a communication unit 43, and a storage unit 44. The storage unit 44 stores context information 45. In addition, the cache information 46 is also stored in the storage unit 44 by processing described later.

Among these, the UI unit 41 displays predetermined information on a display device (not shown) or inputs predetermined operation information. In the present embodiment, since there is no scene in which the UI unit 41 is involved in the operation, the context server 40 may not include the UI unit 41.
The processing unit 42 performs a predetermined process based on information from the communication unit 43 and the like. The processing performed here includes, for example, processing for receiving an acquisition request for the context information 45 from the communication unit 43, extracting the context information 45 from the storage unit 44, and sending it. There is also a process of receiving the cache information 26 from the communication unit 43 and storing it as the cache information 46 in the storage unit 44.

Further, the communication unit 43 transmits / receives information to / from the user client 20.
The storage unit 44 stores various types of information, and such information includes the context information 45 and the cache information 46 as described above. Here, the context information 45 is context information originally managed by the context server 40. The cache information 46 is obtained by transferring and storing the cache information 26 that is information that the user client 20 caches the context information 45.

These functions are realized by cooperation between software and hardware resources. That is, the UI unit 41, the processing unit 42, and the communication unit 43 are realized when a CPU (not shown) of the context server 40 reads a program that realizes these functions from, for example, a magnetic disk into the main memory.
The storage unit 44 can be realized by using various storage media such as a semiconductor memory and a magnetic disk.

Next, the operation of the present embodiment will be described. Here, it is assumed that the user client 20 moves from the environment connected to the context server 40 via the LAN 90 as shown in FIG. 1 to another environment not connected to the context server 40 of FIG. .
In that case, there may be other user clients 20 at the destination. Therefore, in the following, the user client 20 that moves from the environment of FIG. 1 is particularly referred to as a user client 20a, and the user client 20 that is in the destination environment, particularly the user clients 20b, 20c, and 20d. , ...
In addition, there is a case where it is possible to connect to a context server 40 different from the context server 40 of FIG. Therefore, in the following, the context server 40 in the environment of FIG. 1 is particularly referred to as a context server 40a, and the context server 40 in the destination environment is particularly referred to as a context server 40b.

Hereinafter, the operation when the user client 20a moves from the environment of FIG. 1 and shares the context information 45 with the user clients 20b, 20c, 20d,... In another environment will be described for each scene.
[Just before the user client 20a moves from the environment of FIG. 1]
For example, when attending a meeting or the like, the connection with the LAN 90 where the context server 40a exists may have to be disconnected. In such a case, in the present embodiment, the processing shown in FIG. 4 is performed prior to disconnecting the connection with the LAN 90.
FIG. 4A shows an image of the desktop 200 of the user client 20a in this case. That is, first, an icon representing the context server 40 is displayed on the desktop 200. In the figure, the icon 201 represents the context server 40a, and the icon 202 represents another context server 40. Therefore, the user duplicates the icon 201 and creates an icon 203 representing the local cache, as shown by the arrow band in the figure. As a result, as shown in FIG. 4B, the context information 45 is sent from the context server 40a to the user client 20a.

Next, the operation of the user client 20a at this time will be described.
First, when the user instructs to copy the icon 201, the UI unit 21 recognizes this instruction. Then, based on information associated with the icon 201, information (for example, a network address) for connecting to the context server 40a is acquired. Then, when this information is passed to the processing unit 22, the operation of the processing unit 22 is started. Here, the context server 40 and the local cache are represented by icons, but this is merely an example, and any other object may be used.

FIG. 5 is a flowchart showing the operation of the processing unit 22 at this time.
The processing unit 22 acquires information for connecting to the context server 40a from the UI unit 21 (step 211). Then, by transmitting this information to the communication unit 23, an instruction is given to acquire the context information 45 from the context server 40a (step 212). At this time, the user client 20 may be instructed to acquire the context information 45 of all the documents existing, or the context information 45 of the document selected on some basis, such as a recently used document, may be acquired. You may instruct. Thereby, the communication unit 23 requests the context server 40a to transmit the context information 45, and the context server 40a transmits the context information 45 to the user client 20a.

When the context information 45 is transmitted from the context server 40 a, the communication unit 23 receives the context information 45 and passes it to the processing unit 22. Thereby, the processing unit 22 acquires the context information 45 (step 213).
Thereafter, the context information 45 is stored as the cache information 26 in the storage unit 24. Prior to that, the processing unit 22 generates a cache management file 25 for managing the cache information 26 (step 214). .
Then, the processing unit 22 stores the cache management file 25 generated here in the storage unit 24 and also stores the context information 45 in the storage unit 24 as cache information 26 (step 215).

Here, the cache management file 25 generated in step 214 will be described.
FIG. 6 is a diagram showing information managed by the cache management file 25.
That is, the cache management file 25 includes a server ID, a client ID, a cache ID, and a network address.
Among these, the server ID is information for identifying the context server 40 that originally managed the context information 45 cached as the cache information 26 managed by the cache management file 25.
The client ID is information for identifying the user client 20 that stores the cache information 26 managed by the cache management file 25. As will be described later, since the cache information 26 may be transferred to the context server 40, information for identifying the context server 40 may be set in the client ID.

Further, the cache ID is information for identifying the cache information 26 managed by the cache management file 25. Here, the cache ID is given when the cache information 26 is created. That is, different cache IDs are assigned to individual cache information 26 obtained by cutting out the context information 45 managed by the context server 40 at a certain time.
The network address is an address on the network in the current connection status of the device storing the cache information 26 managed by the cache management file 25. That is, it corresponds to reference destination information when referring to the cache information 26. Here, as the network address, an IP address, a Windows (registered trademark) network name, or the like can be used.
The cache management file 25 may include the name of the context server 40 that originally managed the context information 45 in addition to the server ID. In this way, when the predetermined information is displayed with reference to the cache management file 25, the user can easily identify the related context server 40.

[Sharing of context information 45 when the user client 20a moves to an environment without the context server 40]
For example, there may be a network that connects a plurality of user clients 20 at the destination, but the context server 40 does not exist on the network. In such a case, in the present embodiment, processing as shown in FIG. 7 is performed. In other words, the user client 20a leaves the environment in which the context server 40a exists while holding the cache information 26. In the destination environment, the user client 20a copies the cache management file 25 and transmits the copy to the other user client 20b. Accordingly, the user client 20a behaves as a temporary context server that provides the cached context information 45.

Next, the operation of the user client 20a at this time will be described.
First, when the user instructs to copy the cache management file 25, the UI unit 21 recognizes this instruction. Note that the duplication instruction here may be performed by an existing method. Then, when this operation information is passed to the processing unit 22, the operation of the processing unit 22 is started.

FIG. 8 is a flowchart showing the operation of the processing unit 22 at this time.
The processing unit 22 receives an instruction to copy the cache management file 25 from the UI unit 21 (step 221).
As a result, the processing unit 22 acquires the network address of the current user client 20a (step 222), and replaces the network address in the cache management file 25 with the acquired network address (step 223). That is, the cache management file 25 generated in the environment connected to the context server 40a includes the network address in that environment, but has been rewritten to the network address in the current connection status because the environment has been moved. . However, if the network address has already been updated, it need not be updated.

  Thereafter, the processing unit 22 generates a copy of the cache management file 25 (step 224). Then, the cache management file 25 that is a copy is transmitted to the user client 20b in accordance with a user instruction (step 225). Here, the cache management file 25 can be transmitted using e-mail, for example. Alternatively, the cache management file 25 may be transmitted to the user client 20b by performing a predetermined operation on the icon 203 representing the local cache shown in FIG.

[Sharing of Context Information 45 when User Client 20a Moves to Environment with Context Server 40]
For example, in addition to a network connecting a plurality of user clients 20 at the destination, there may be a context server 40b other than the context server 40a on the network. In such a case, in the present embodiment, processing as shown in FIG. 9 is performed.

  FIG. 9A shows an image of the desktop 200 of the user client 20a in this case. That is, first, an icon representing the context server 40 and an icon representing the local cache are displayed on the desktop 200. In the figure, the icon 201 represents the context server 40a, and the icon 202 represents the context server 40b. An icon 203 represents a local cache. Therefore, the user clicks the mouse on the icon 203, drags it to the icon 202, and drops it there, as indicated by the band of arrows in the figure. As a result, as shown in FIG. 9B, the cache information 26 is sent from the user client 20a to the context server 40b. Thereby, the context server 40b behaves as a temporary context server that provides the cached context information 45.

Next, the operation of the user client 20 at this time will be described.
First, when the user drags and drops the icon 203 onto the icon 202, the UI unit 21 recognizes this operation. Then, based on the information associated with the icon 202, information (for example, a network address) for connecting to the context server 40b is acquired. Then, when this information is passed to the processing unit 22, the operation of the processing unit 22 is started. Here, the context server 40 and the local cache are represented by icons, but this is merely an example, and any other object may be used.

FIG. 10 is a flowchart showing the operation of the processing unit 22 at this time.
The processing unit 22 acquires information for connecting to the context server 40b from the UI unit 21 (step 231), and retrieves the cache information 26 from the storage unit 24 (step 232). Then, by transmitting the information from the UI unit 21 and the cache information 26 to the communication unit 23, the context server 40b is instructed to transmit the cache information 26 (step 233). As a result, the communication unit 23 transmits the cache information 26 to the context server 40 b, and the context server 40 b stores the cache information 26 as the cache information 46 in the storage unit 44.
When the cache information 26 is transmitted to the context server 40b, the processing unit 22 rewrites the client ID in the cache management file 25 with the server ID of the context server 40b and rewrites the network address with the network address of the context server 40b (step 234).

[Reference from the user clients 20b, 20c, 20d,... To the cache information 26 held by the user client 20a]
First, a scene where the cache information 26 shared between a plurality of user clients 20 is used will be described.
FIG. 11 is a diagram showing an example of such a scene.

Among these, FIG. 11A shows a scene in which the user client 20a functions as a “simple server” that provides the cache information 26 because the user clients 20a, 20b, 20c, and 20d cannot connect to the context server 40a. It is a thing. That is, the user clients 20b, 20c, and 20d refer to the cache information 26 held by the user client 20a based on the cache management file 25 held by the user clients 20b, 20c, and 20d.
FIG. 11B shows a case where the context server 40b functions as an “alternative server” that provides the cache information 46 because the user clients 20a, 20b, and 20c cannot connect to the context server 40a. . That is, the user clients 20b and 20c refer to the cache information 46 held by the context server 40b based on the cache management file 25 held by the user clients 20b and 20c.

Next, operations of the user clients 20a, 20b, 20c, and 20d at this time will be described. However, here, the user clients 20a, 20b, 20c, and 20d will be described using the user client 20 as a representative.
First, when the user performs an operation of opening a document held in the user client 20, the UI unit 21 recognizes this operation. Then, when the operation information is passed, the operation of the processing unit 22 starts.

FIG. 12 is a flowchart showing the operation of the processing unit 22 at this time.
As described above, information (for example, server ID and context ID) for accessing context information is added to the document. Therefore, the processing unit 22 takes out information for connecting to the context server 40 from the document (step 241). Then, using this information, a connection to the context server 40 is attempted, and it is determined whether or not the connection to the context server 40 has been established (step 242).
As a result, when it is determined that the connection to the context server 40 has been established, the context information 45 managed by the context server 40 is acquired (step 243).

  On the other hand, when it is determined that the connection to the context server 40 could not be established, it is determined whether or not the cache management file 25 including the server ID extracted in step 241 is stored in the storage unit 24 of the own device (step 244). That is, it is determined whether the context information 45 to be referred to is cached by any user client 20 and the cache management file 25 for sharing the cache has not been transferred to the own device. If it is determined that the cache management file 25 including the server ID is not stored in the storage unit 24, the process is terminated as it is. If it is determined that the cache management file 25 is stored, the cache management file 25 is stored in the cache management file 25. It is determined whether or not the included client ID matches the ID of its own device (step 245).

If the client ID in the cache management file 25 matches the ID of the own device, the context information 45 is acquired from the cache information 26 stored in the storage unit 24 of the own device (step 246). If the client ID in the cache management file 25 does not match the ID of its own device, the network address is first obtained from the cache management file 25 (step 247). Then, the context information 45 is acquired from the cache information 26 stored in the storage unit 24 of the device specified by this network address (step 248). When the context information 45 is not managed by the alternative server, the network address of the other user client 20 is acquired in step 247, and the context information 45 is acquired from the other user client 20 in step 248. become. On the other hand, when the context information 45 is managed by the alternative server, in step 247, the network address of the context server 40b is acquired, and in step 248, the context information 45 is acquired from the context server 40b.
This is the end of the description of the present embodiment.

In the present embodiment, the user client 20a caching the context information 45 may be able to connect to the context server 40a again thereafter. In such a case, the cache information 26 may be transmitted from the user client 20a to the context server 40a, and the context information 45 in the context server 40a may be updated.
It is also conceivable that the context server 40b, which is transferred as the context information 45 and functions as an alternative server, can communicate with the original context server 40a thereafter. Even in such a case, the cache information 46 can be transmitted from the context server 40b to the context server 40a, and the context information 45 in the context server 40a can be updated. However, for that purpose, it is necessary to transmit not only the cache information 26 but also the cache management file 25 to the context server 40b in step 233 of FIG.

As described above, in this embodiment, the context information in the context server is collectively cached before leaving the network. As a result, the context information can be temporarily used in an offline state.
Note that the timing at which the context information is cached may be a time point when the document is opened and the context information is referred to. However, there is a possibility that the cache cannot be referred to when its expiration date has expired. Therefore, in order to leave the information to be used in the cache, it is necessary to check one by one before going offline, whether or not the cache can be used in the offline state. This embodiment eliminates such a troublesome confirmation work, and has a marked effect even when compared with a technique of caching when a document is opened.

  In this embodiment, the management file for referencing the cached context information is duplicated and distributed to other user clients. As a result, a plurality of users can use the context information on a network in which no context server is installed.

  Furthermore, in this embodiment, the context (dynamic information) is acquired based on the document (static information) on the local machine. As a result, the range of the acquired cache can be easily grasped, and a practical cache can be easily generated. In a general-purpose system that is difficult to limit the range, such as a Web browser, it is not practical to share a small cache on the local machine, but it is based on static and easy-to-share data such as documents. Dynamic data (context) is practical in a meeting situation even if it is a cache on the local machine.

It is the figure which showed the structure of the computer system used as the premise of embodiment of this invention. It is the figure which showed the function structure of the user client in embodiment of this invention. It is the figure which showed the function structure of the context server in embodiment of this invention. It is the figure which showed the mode at the time of a user client acquiring context information from a context server in embodiment of this invention. It is the flowchart figure which showed the operation | movement at the time of a user client acquiring context information from a context server in embodiment of this invention. It is the figure which showed the information content of the cache management file produced | generated by embodiment of this invention. It is the figure which showed the mode at the time of a user client sharing context information with another user client in embodiment of this invention. It is the flowchart which showed the operation | movement at the time of a user client sharing context information with another user client in embodiment of this invention. It is the figure which showed the mode at the time of a user client transmitting context information to another context server in embodiment of this invention. It is the flowchart which showed the operation | movement at the time of a user client transmitting context information to another context server in embodiment of this invention. It is the figure which showed the mode at the time of a user client referring the context information in another apparatus in embodiment of this invention. It is the flowchart which showed the operation | movement at the time of a user client referring the context information in another apparatus in embodiment of this invention.

Explanation of symbols

10 ... provider client, 20 ... user client, 30 ... document server, 40 ... context server

Claims (9)

An information processing terminal that acquires and uses context information from a server that manages context information that is dynamically changing information about a document,
Display means for displaying an object representing the server;
Communication means for receiving the context information from the server in response to a user operation on the object;
An information processing terminal comprising storage means for storing the context information received by the communication means.   In response to an instruction to share the context information stored in the storage unit with another information processing terminal, the communication unit transmits a management file for referring to the context information to the other information processing The information processing terminal according to claim 1, wherein the information processing terminal is transmitted to the terminal. The display means displays other objects representing servers other than the server,
The communication unit transmits the context information stored in the storage unit to the other server in response to a user operation regarding the other object,
The information processing terminal according to claim 1, wherein the storage unit stores a management file for referring to the context information transmitted to the other server. An information processing terminal that acquires and uses context information, which is dynamically changing information about a document,
Storage means for storing a management file for referring to the context information;
Communication means for transmitting a reference request for the context information stored in another server other than the management server or an information processing terminal based on the management file when connection to the context information management server is not possible; An information processing terminal characterized by that. A method in which information processing terminals share context information, which is dynamically changing information about documents, with other information processing terminals,
The information processing terminal caching the context information from a server that manages the context information;
The information processing terminal generating a management file for referring to the cached context information;
The information processing terminal includes the step of transmitting the generated management file to the other information processing terminal. A program for realizing a predetermined function in an information processing terminal that acquires and uses context information from a server that manages context information that is dynamically changing information about a document,
A function of acquiring the context information from the server according to a user instruction;
A program for realizing a function of caching the acquired context information.   Further realizing a function of transmitting a management file for referring to the context information to the other information processing terminal in response to an instruction to share the cached context information with the other information processing terminal. The program of Claim 6 for. A function of transmitting the cached context information to another server in response to a user instruction;
The program according to claim 6, further realizing a function of storing a management file for referencing the context information transmitted to the other server in a predetermined storage area. A program for realizing a predetermined function in an information processing terminal that acquires and uses context information that is dynamically changing information about a document,
A function for identifying other servers or information processing terminals that cache the context information other than the context information management server;
A program for realizing a function of transmitting a reference request for the context information cached in the specified other server or information processing terminal.

Images