JP5088269B2 - Screen information management method - Google Patents

Description

  The present invention relates to a method and apparatus for managing screen information. For example, the present invention can be applied to a method and apparatus for managing screen information including data input using a Web application.

  Currently, a lot of information is stored and disclosed on the Internet, and as the sources of information diversify, it becomes difficult to accurately find out information that is of interest to users from this vast amount of information. ing. For this reason, a search site for searching information on the Internet using a keyword or the like is indispensable, and many users depend on this search function. And it can be said that the most effective means to register information to be shared widely is a search site.

  On the other hand, an application program called a Web application that uses a screen displayed on a browser as an input screen has been used. A typical example is an in-house order processing system. Processing that is conventionally realized as a client-server type application is realized by using a Web function, and a browser is often used as a client.

  As Web applications become more and more used, there is a demand for sharing and reusing information input thereto. For example, it is useful if the estimated amount acquired for purchasing a certain product, information on delivery date, information on necessary accessories, etc. can be widely shared not only by the person in charge of purchase but also throughout the company. In a large-scale company, there is a case where a search server is prepared in the company to share information, and it is desirable that the contents input to the Web application can be searched by such a search server.

  As a related technique, in the method described in Patent Document 1, screen data input by a terminal operator through a screen from a terminal device is saved. Then, the screen data saved according to an arbitrary instruction from the terminal operator is restored.

  In the system described in Patent Document 2, the terminal stores each input state performed by the operator for each input field on the screen. Thereafter, the input state is automatically reproduced for input fields on the same screen.

When the operator requests saving of the transaction input screen, the terminal control device provided in the automatic transaction system described in Patent Literature 3 allows the operator to input information about the transaction input screen after inputting a save number and an explanatory note. To save.
JP-A-5-94275 JP-A-11-184608 JP 2000-123221 A

In the currently widely used search technology on the Internet, the search server refers to all Web pages to be searched in advance, and an index is created using information such as keywords extracted from the contents. If there is a search request from the user, a matching page is obtained from this index, and a list of URLs of the obtained pages is returned to the user.

  However, when this search method is applied to a Web application, the following problem occurs. In other words, Web applications generally require user authentication and often require input of an ID or password. However, the index creation process of the search site assumes only normal pages and cannot refer to pages that require authentication. Therefore, the screen of the Web application cannot be a search target.

  In addition, information to be shared in the Web application is information input by the user, and is not a screen displayed on the Web application side. Even if the access permission is granted to the search server so that the Web application screen can be referred to, the information sent by the Web application to the search server is the state before the user inputs (that is, the value of each item). Is the default screen). For this reason, the search server cannot refer to the screen after the user inputs information. In addition, since the screen in which the user has entered information is only held inside the browser, the search server mechanism that targets the contents existing on the server essentially does not use the Web application. Cannot refer to the information entered using.

  In response to a request to share information, a function of inquiring input information and displaying it on a screen is known. However, an ID for using the Web application is required, and the Web application must be operated to make an inquiry. For this reason, automatic index creation by a search site is impossible, and information input using a Web application cannot be a search target. In addition, it is possible to modify a large number of currently running applications and add an input information list function that can be referred to from the search server, but it requires a lot of man-hours and is not realistic. Further, even when the function of saving the contents of a page as a file is used, what is saved is the initial value of the page contents and is in a state before the user inputs. Therefore, even if this file is referenced, the input information cannot be saved or shared.

  The methods described in Patent Documents 1 to 3 described above only provide a function of reusing contents input in the past when the same application or terminal is used. Therefore, in order to share information, a specific web application must be used.

  As described above, in the related art, it is difficult to share information input using a Web application. That is, in the prior art, as shown in FIG. 28, for example, information input using a Web application is not a search target of the search server. For this reason, in order to search for information input using a certain Web application, it is necessary to call a reference function provided by the same or corresponding application. Therefore, the burden of information retrieval was great.

  An object of the present invention is to provide a method for easily searching for information input using a Web application.

  The screen information management method of the embodiment is executed by a relay server connected to a client terminal and an application server via a network. The relay server forwards the page request received from the client terminal to the application server, receives an HTML file that is a response to the page request from the application server, and a predetermined by a user of the client terminal Inserting into the HTML file a script describing a process for transmitting the display screen information of the client terminal to the relay server based on the instruction, and transmitting the HTML file with the script inserted to the client terminal Receiving display screen information from the client terminal, recording step for recording the display screen information in a recording means, and generating link information to the display screen information recorded in the recording means, List information The method comprising the steps of: public and generates a list screen, to run.

  The script may transmit the contents of the DOM tree displayed by the browser of the client terminal to the relay server as the display screen information.

  According to the disclosed method, information input using a Web application can be easily searched.

  In the screen storage method of the embodiment, a function of transmitting information on a screen being displayed (including data input by a user) to the screen storage server is added to the browser. The screen storage server stores and publishes information on the screen. This enables centralized information sharing by the search server including data input to the Web application and processing results. Specifically, it is as follows.

  A screen saving function is added to the browser. The screen storage function reads the contents of a DOM (Document Object Model) tree that is currently displayed by the browser in accordance with an instruction from the browser user, and transmits the contents to the screen storage server. In this configuration, the screen content is acquired on the browser side. For this reason, including the value being input in the input field, the contents held in the browser at that time are acquired. In addition, since this screen saving function is added not to the Web application side but to the browser side, the screen contents can be transmitted to the screen saving server without depending on the Web application.

  The screen storage server functions as an HTML server and stores the received screen content as an HTML format file. Then, the screen storage server publishes the stored file as a Web page, and adds the URL of the file to its list page in order to enable reference from the search server. As a result, the input screen of the Web application (including information input by the user) can be referred to as information published by the screen storage server via the search server. That is, information input to the Web application can be shared using the search server. At this time, in order to realize this function, it is not necessary to make a change on the Web application side, and it can be applied as it is to an arbitrary Web application.

  The method for adding the screen saving function to the browser is realized by preparing a relay server that acts as a proxy server for the browser and transmitting a script that provides the screen saving function from the relay server to the browser. In this case, the relay server inserts a JavaScript code or the like that implements the screen storage function into the screen HTML that the Web application transmits in response to the request from the browser, and transmits the screen HTML to the browser. Alternatively, the method of adding the screen saving function to the browser may be realized by registering a program that provides the screen saving function in the bookmarklet. In this case, a program in a script language or the like is registered in the browser in advance, and the screen saving function is called according to a user instruction.

<First Embodiment>
FIG. 1 is a diagram illustrating a configuration of a system in which the screen storage method according to the first embodiment is used. In FIG. 1, a Web application server 201 provides a corresponding application in response to a request from a browser. However, the Web application server 201 includes user authentication information and provides an application only to a user who has been successfully authenticated. The search server 202 searches for a corresponding website or the like according to a search request sent from the browser, and provides the search result to the browser.

  Browser devices (user terminals) 101 and 102 are computer terminals that implement a browser program, and are connected to a network. The browser apparatus 101 inputs information using a Web application provided by the Web application 201. Information input using the Web application in the browser apparatus 101 will be described in detail later, but is stored in the screen information storage server 1 and released to the search server 202 in accordance with a user instruction. Then, the browser apparatus 102 can refer to information input in the browser 101 via the search server 202.

  The screen information storage server 1 includes a relay function unit 10, a screen information storage unit 20, an HTML server unit 30, and an authentication unit 40. The relay function unit 10 includes a request reception unit 11, a request transmission unit 12, a page content reception unit 13, and a page content transmission unit 14, and operates as a proxy server for the browser.

  That is, a request for a page transmitted from the browser device 101 is received by the request reception unit 11. The accepted request is retransmitted by the request transmission unit 12 to the corresponding host. In this embodiment, the request received from the browser device 101 is transferred to the Web application server 201. Then, the web application server 201 performs user authentication as necessary, and then returns the response content (that is, page content) to the request to the screen information storage server 1. The page content receiving unit 13 receives page content from a corresponding host (here, the Web application server 201). Then, the page content transmission unit 14 transmits the received page content to the browser device 101. Thereby, the browser apparatus 101 can browse the requested page, and can use the requested Web application.

  The relay function unit 10 further includes a script storage unit 15 and a script addition unit 16. The script storage unit 15 stores a screen save script for causing the browser to save screen information. The script adding unit 16 is provided between the page content receiving unit 13 and the page content transmitting unit 14, and determines whether or not the response content is in the HTML format. If the response content is in the HTML format, the script adding unit 16 extracts the screen saving script from the script storage unit 15 and adds the script to a predetermined position of the page content. The screen saving script is inserted, for example, immediately before the </ head> tag of the HEAD part. In this case, the page content transmission unit 14 transmits the page content to which the screen saving script is added to the browser device 101.

  FIG. 20 is a flowchart showing the operation of the relay function unit. In step S1, a page request is received from the browser. In step S2, the host name of the request destination is acquired. In step S3, a page request is transmitted to the request destination host. The host that has received this request returns response contents (that is, page contents).

In step S4, the response content is received from the host. In step S5, it is checked whether or not the response content is in HTML format. If the response content is in the HTML format, it is checked in step S6 whether the terminal symbol of the HEAD element (ie, </ head>) exists in the response content. If a terminal symbol of the HEAD element exists in the response content, a screen save script is inserted immediately before the terminal symbol of the HEAD element in step S7. In step S8, the response content in which the screen saving script is inserted is transmitted to the browser.

  FIG. 2 shows an example of page contents transmitted by the Web application server 201. In this embodiment, it is assumed that a page for a product ordering application is requested by the browser device 101. Therefore, this page content describes the screen content to be displayed on the browser device 101. This page content is received by the page content receiving unit 13 of the relay function unit 10. An example of the screen display when this page content is sent to the browser is shown in FIG. In this embodiment, an input area for inputting “orderer”, “model number”, “unit price”, “number”, and “release source”, a button for receiving a user instruction, and the like are displayed.

  However, as described above, the screen information storage server 1 of the embodiment has a function of adding a screen storage script to the page content from the Web application server 201. An example in which a script is added to the page content is shown in FIG. In this embodiment, the screen saving script is inserted immediately before the terminal symbol (that is, </ head>) of the HEAD element as described above.

  FIG. 5 is an example of a screen saving script. The screen saving script has an input reception process, a display content reading process, a screen information transmission process, and an initialization process. In the input reception process, the screen saving function is activated when a specific key (here, the F12 key) is pressed on the browser device 101. In the display content reading process, screen information (HTML data) related to the display content is acquired. The screen information to be acquired includes information input by a user using a Web application in the browser apparatus 101. In the screen information transmission process, the acquired screen information is transmitted to a designated URL. In this embodiment, the screen information transmission destination is an address (screens.mycompany.com/postpage.cgi) in the screen information storage server 1. In addition, page information (document.URL) is included as screen information to be transmitted.

  The screen save script described above does not change the displayed screen content. Therefore, when the page content to which the screen saving script is added is transmitted to the browser device 101, the content displayed on the browser screen is the same as that in FIG. Further, the script added to the page content may be only the function of downloading the main body of the screen saving script saved as a separate file.

  FIG. 6 is a diagram illustrating the configuration and operation of the browser. The browser 110 is implemented in the browser device 101 shown in FIG. 1, and has a function of creating and transmitting a page request in accordance with a user instruction, and a function of receiving and interpreting the page content corresponding to the page request. Yes.

  The page content received from the proxy server (that is, the screen information storage server 1 shown in FIG. 1) is interpreted by the browser 110. The content to be displayed is held in the display content holding unit 111 as tree structure information with the HTML element as the highest level, and is referred to when the screen is displayed. The contents to be executed are held in the in-page script holding unit 112. The script held in the in-page script holding unit 112 includes a Web application script 113 included in the contents of the Web application and a screen saving script 114 added in the screen information saving server 1.

The screen saving script 114 includes an initialization processing unit 115, an input receiving unit 116, a display content reading unit 117, and a screen information transmission unit 118. The initialization processing unit 115 is executed when the screen saving script 114 is read into the browser 110, and sets necessary information for the browser so that the input receiving unit 116 is called upon input from the user. The input receiving unit 116 checks the input from the user and calls the display content reading unit 117 when the input is to call a predetermined screen saving function. The display content reading unit 117 acquires screen information (that is, display content displayed on the display device of the browser device 101) and passes it to the screen information transmission unit 118. This screen information includes data input by a user using a Web application. Then, the screen information transmitting unit 118 transmits the screen information acquired by the display content reading unit 117 to the designated URL. In this embodiment, the screen information is transmitted to the screen information storage server 1. In the screen saving script shown in FIG. 5, the screen saving function is executed when the user presses the twelfth function key of the browser device 101.

  FIG. 21 is a flowchart showing browser initialization processing. In step S11, functions required when the input reception process, the display content reading process, and the screen information transmission process are executed are defined. In step S12, an input instruction process called at the time of key input is added to the frame element displayed on the display device of the browser device 101. In step S13, information for identifying the user is stored in a variable prepared in advance.

  FIG. 22 is a flowchart showing the input reception process. In step S21, it is checked whether or not the key pressed by the user of the browser apparatus 101 is “F12”. When the F12 key is pressed, the display content reading process is called in step S22, and the screen information transmission process is called in step S23.

  FIG. 23 is a flowchart showing the display content reading process. In the display content reading process, the display elements held by the display content holding unit 111 are extracted, and all the contents of the tree structure are converted into character strings that can be transmitted to the screen information storage unit 20 and connected in order. That is, in step S31, the <HTML> element that is the highest level of the display content is extracted as a target element. In step S32, the tag name, attribute name, and value of the target element are converted into character strings and connected. In step S33, the child elements of the target element are traced in order, and the extracted contents are converted into character strings and connected. This process is repeated for each child element. In step S34, the closing tag of the target element is converted into a character string and connected.

  FIG. 7 is an example of the input screen of the browser. In this embodiment, "Yamada Taro", "PC-100", "150,000", "1", and "ABC PC Sales" as "Orderer", "Model Number", "Unit Price", "Number", and "Distributor", respectively, according to the usage document of the browser 110. "Is entered. “Domestic” is selected.

  FIG. 8 shows an example of characterizing the screen shown in FIG. The character string screen information includes information input by the user using a Web application. Information input by the user is written at a predetermined position in the page content received from the Web application server 201.

  FIG. 24 is a flowchart showing the screen information transmission process. In the screen information transmission process, a character string representing the screen information is transmitted to the access URL of the screen information storage unit 20 designated in advance. At this time, accompanying information such as the URL of the Web application used by the user may be transmitted together with the screen information. That is, in step S41, an argument is generated using the URL of the page displayed on the display device of the browser device 101 and a character string representing the display content. In step S42, the generated argument is transmitted as a POST request to the URL of the screen information storage unit 20. In step S43, a new window is opened and the response content from the screen information storage unit 20 is displayed.

  As described above, when the browser 110 of the browser apparatus 101 transmits a page request to the Web application 201, the browser 110 receives the screen saving script together with the corresponding page content. The screen saving script converts the screen information representing the display content of the screen of the display device of the browser device 101 into a character string and transmits it to the screen information saving server 1. The transmitted screen information includes information input by the user to the Web application. Thereby, the screen information storage unit 20 of the screen information storage server 1 receives screen information including information input by the user.

  As shown in FIG. 1, the screen information storage unit 20 includes a screen information reception unit 21, an information storage unit 22, and a list creation unit 23. The screen information reception unit 21 receives the screen information transmitted from the browser 110 and stores it in the information storage unit 22. The screen information stored in the information storage unit 22 is given a URL to be disclosed by the HTML server unit 30. This URL is generated, for example, using additional information such as the URL of the target Web application, the storage date and time, and the user name. The user name is specified from, for example, a prior authentication procedure or a user ID registered in advance. An example of information stored in the information storage unit 22 is shown in FIG. In this embodiment, the user name, page ID, storage date / time, and directory name are recorded for each screen information. In this embodiment, the page ID is generated based on a character string and a URL that identify a Web application used via a browser.

  The URL generated for each screen information is passed to the list creation unit 23. The list creation unit 23 adds the received URL to the list file published by the HTML server unit 30. An example of the list file is shown in FIG. In this embodiment, URLs assigned to the six pieces of screen information are registered. In this embodiment, these URLs are classified and registered for each page ID and each storage date. A display example of the list file shown in FIG. 10 is shown in FIG.

  FIG. 25 is a flowchart showing screen information storage processing executed in the screen storage server 1. In step S51, the screen information transmitted from the browser is received. In step S52, a URL to be added to the screen information is generated from the user information, the target URL name, the reception date and time, and the like. User information identifies the user of the browser. The target URL identifies, for example, a Web application used by the browser. The reception date and time may be the date and time when the screen information is stored in the information storage unit 22. In step S53, the contents of the screen information are stored in the information storage unit 22, and the URL generated in step S52 is assigned. Thereby, the stored screen information can be referred to by using the assigned URL. In step S54, the list page (list file shown in FIG. 10) is updated, and the URL generated in step S52 is added. As a result, the screen information received from the browser is released to the HTML server unit 30.

  The HTML server unit 30 publishes the above-described list page and each screen information to the network. That is, the request receiving unit 31 receives a request from the search server 202. The page content transmission unit 32 returns the list page created in the screen information storage unit 20 in response to a request from the search server 202. Therefore, the search server (search server 202 shown in FIG. 1) existing on the network can create an index by referring to the list page and the screen information page linked from the list. Therefore, if another user searches the search server 202 by inputting “PC-100” as a keyword, for example, the input screen of this Web application is included in the search result, and the contents are referred to. be able to. An embodiment in which another user's browser displays screen information stored in the screen storage server 1 is shown in FIG.

In this way, another user's browser (browser device 102 shown in FIG. 1) can refer to the screen information stored in the screen storage server 1 via the search server 202. At this time,
The screen information stored in the screen storage server 1 includes data input by using the Web application in the browser device 101. Therefore, the browser device 102 can refer to screen information including data input using the Web application in the browser device 101 only by using a general search function without using a specific application. it can.

  The screen storage server 1 implements the authentication unit 40 shown in FIG. 1 in order to authenticate the user. The authentication unit 40 includes an authentication execution unit 41, a user authentication information storage unit 42, and a session management table 43. When the user uses the screen saving function, the user calls the authentication execution unit 41 prior to the use. The authentication execution unit 41 requests a user ID and password from the calling user, and collates with the user authentication information stored in the user authentication information storage unit 42. If the authentication is successful, the user is registered in the session management table 43. Thereafter, the session management table 43 is referred to in order to determine whether or not to execute the script addition process. For example, in the flowchart shown in FIG. 20, it is determined whether or not the user is registered in the session management table 43, and steps S5 to S7 may be executed only when the user is registered. The session management table 43 is also referred to for user identification in the screen information storage process. Note that the session information is discarded at an appropriate timing such as termination of the browser or elapse of a predetermined time.

<Second Embodiment>
In the first embodiment, a relay device that operates as a proxy server has a function of transmitting a screen saving script and a function of saving / disclosing screen information. On the other hand, in the second embodiment, it is not necessary to provide a proxy server. However, the bookmarklet function provided in the browser is used.

  FIG. 13 is a diagram illustrating a configuration of a system in which the screen saving method according to the second embodiment is used. The screen storage server 2 of the second embodiment includes a script providing unit 50 in addition to the screen storage unit 20, the HTML server unit 30, and the authentication unit 40. Here, the configurations and operations of the screen storage unit 20, the HTML server unit 30, and the authentication unit 40 are the same as those in the first embodiment. Further, the screen storage server 2 of the second embodiment need not include the relay function unit 10 shown in FIG.

  The request reception unit 51 receives a script reference request from the browser. The script storage unit 52 stores a screen saving script. This screen saving script is equivalent to the first embodiment, and is as shown in FIG. 5, for example. Then, the script transmission unit 53 transmits the screen storage script to the browser that issued the script reference request. As described above, the script providing unit 50 provides a screen saving script in response to a request from the browser. The script providing unit 50 may provide the screen saving script only to the user authenticated by the authentication unit 40.

  Further, the script providing unit 50 publishes a Web page including the bookmark as a link in order to facilitate registration with the bookmark in the browser. An example of the contents of this Web page is shown in FIG. An example in which this Web page is displayed by a browser is shown in FIG. In this embodiment, as shown in FIG. 15, a link for calling the “screen saving function” is registered in the browser by right-clicking.

FIG. 16 is a diagram for explaining the configuration and operation of a browser used in the second embodiment. The display content holding unit 111 and the in-page script holding unit 112 hold the contents of the page received from the Web application server 201 as in the first embodiment. In the bookmarklet function unit 121, a storage function reading unit 122 is registered as a bookmarklet. An example of the contents of this bookmarklet is shown in FIG. Here, in general, the length of the bookmarklet is limited. For this reason, the bookmarklet code of this embodiment is described to request the screen saving script from the script providing unit 50 and execute it.

  In the browser device configured as described above, the user executes a Web application. Then, it is assumed that the user saves the screen information when the input screen of the Web application is displayed. In this case, the user activates a bookmark for saving a screen via the bookmark activation unit 130. Then, the bookmarklet function unit 121 executes the script of the storage function reading unit 122 in accordance with a user instruction.

  FIG. 26 is a flowchart showing the saving function reading process activated from the bookmarklet. In step S61, a script element is added to the contents of the displayed page. In step S62, the URL of the screen saving script is designated as the content of the added script element. This URL is specified in the bookmarklet shown in FIG. In step S63, the screen saving script is called from the designated URL. In this embodiment, a script reference request is transmitted to the script providing unit 50 of the screen storage server 2.

  When the script of the storage function reading unit 122 is executed, the screen storage script 123 is read. An example of the screen saving script 123 is shown in FIG. The screen saving script 123 includes, for example, the display content reading unit 117 and the screen information transmission unit 118 of the first embodiment.

  FIG. 27 is a flowchart illustrating screen saving processing according to the second embodiment. In step S71, a display content reading process is called to convert the display content into a character string. In step S72, a screen information transmission process is called, and the display content converted into a character string is transmitted to the screen information storage unit of the screen storage server. The operations of the display content reading unit 117 and the screen information transmission 118 are the same as those in the first embodiment.

  As described above, in the second embodiment, the screen storage function can be requested at a timing desired by the user (for example, when using a Web application). In response to this request, the browser receives and executes the screen saving script. As a result, as in the first embodiment, screen information including data input using a Web application is stored / published on the screen storage server.

<Hardware configuration>
FIG. 19 is a diagram illustrating a hardware configuration of a computer that implements the screen storage servers 1 and 2 according to the embodiment. In FIG. 19, the CPU 301 uses the memory 303 to execute a program describing the processing of the flowchart described above. The storage device 302 is a hard disk, for example, and stores the program. Note that the storage device 302 may be an external recording device. The memory 303 is a semiconductor memory, for example, and includes a RAM area and a ROM area.

  The reading device 304 accesses the portable recording medium 305 in accordance with an instruction from the CPU 301. The portable recording medium 305 includes, for example, a semiconductor device (such as a PC card), a medium to / from which information is input / output by a magnetic action, and a medium to / from which information is input / output by an optical action. The communication interface 306 transmits / receives data via a network in accordance with instructions from the CPU 301. The input / output device 307 corresponds to a display device, a device that receives an instruction from a user, and the like.

The program executed in the screen storage servers 1 and 2 is provided in the following form, for example.
(1) Installed in advance in the storage device 302.
(2) Provided by the portable recording medium 305.
(3) Download from the program server 310.
The screen storage servers 1 and 2 according to the embodiment are realized by executing the above program on the computer having the above configuration.

<Others>
The screen saving function may be added to the browser by other methods. For example, the content of the Web application may be relayed by accessing the relay device (relay function unit) from a browser and specifying the URL of the Web application as an argument. When the browser has a function for registering / executing a script in addition to the bookmarklet, the screen saving script may be registered and executed in advance using the registration / execution function.

  In addition, when it is desired to limit the range in which information is disclosed, a user authentication function is provided in the screen information storage unit and the HTML server unit of the above-described embodiment. Then, a list page may be dynamically configured according to a reference authority predetermined for each user so that only pages permitted to be used by the user can be viewed. In this case, since there is information that cannot be referred from a general search server, convenience is lowered. However, if the HTML server part of the present embodiment is referred to in addition to the search server, all information disclosed can be referred to.

<Effects of Screen Saving Method of Embodiment>
In the prior art, information generated using a Web application has not been searched by a general search server. For this reason, when searching for information generated using a Web application, conventionally, as shown in FIG. 28, it has been necessary to call a query function provided in the application using the corresponding Web application. . Therefore, the burden at the time of information retrieval was large.

  On the other hand, if the screen saving method of the embodiment is introduced, information input to the Web application can be searched by the search server. Therefore, information can be widely shared. In addition, since the contents of the screen being operated can be stored and shared, it is possible to realize work efficiency by recording and reusing operations across a plurality of screens.

It is a figure which shows the structure of the system by which the screen preservation | save method concerning 1st Embodiment is used. It is an Example of the page content which a web application server transmits. It is an example of the screen display corresponding to the page content shown in FIG. It is an example of the page content to which the script is added. It is an Example of a screen preservation | save script. It is a figure explaining a structure and operation | movement of a browser. It is an Example of the input screen of a browser. It is an Example of characterizing the screen shown in FIG. It is an Example of the information stored in an information storage part. It is an Example of a list file. It is a display example of the list file shown in FIG. This is an embodiment in which screen information stored in a screen storage server is displayed on another user's browser. It is a figure which shows the structure of the system by which the screen preservation | save method concerning 2nd Embodiment is used. It is an Example of the page for delivering a bookmarklet. It is a display example of the page shown in FIG. It is a figure explaining the structure and operation | movement of a browser used in 2nd Embodiment. It is an example of the bookmarklet for a screen preservation | save function. It is an Example of the screen preservation | save script in 2nd Embodiment. It is a figure which shows the hardware constitutions of a screen storage server. It is a flowchart which shows operation | movement of a relay function part. It is a flowchart which shows the initialization process of a browser. It is a flowchart which shows an input reception process. It is a flowchart which shows a display content read-out process. It is a flowchart which shows a screen information transmission process. It is a flowchart which shows a screen information preservation | save process. It is a flowchart which shows the preservation | save function reading process started from a bookmarklet. It is a flowchart which shows the screen preservation | save process in 2nd Embodiment. It is a figure explaining the problem of a prior art.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1, 2 Screen information storage server 10 Relay function part 11 Request reception part 12 Request transmission part 13 Page content reception part 14 Page content transmission part 15 Script storage part 16 Script addition part 20 Screen information storage part 21 Screen information reception part 22 Information storage Unit 23 List creation unit 30 HTML server unit 40 Authentication unit 50 Script provision unit 51 Request reception unit 52 Script storage unit 53 Script transmission unit 101 Browser device 110, 120 Browser 114, 123 Screen saving script 115 Initialization processing unit 116 Input reception unit 117 Display content reading unit 118 Screen information transmission unit 121 Bookmarklet function unit 122 Save function reading unit 201 Web application server 202 Search server

Claims (2)

A screen information management method executed by a relay server connected to a client terminal and an application server via a network,
The relay server is
Transferring the page request received from the client terminal to the application server and receiving an HTML file that is a response to the page request from the application server;
Inserting a script describing a process of transmitting display screen information of the client terminal to the relay server based on a predetermined instruction by a user of the client terminal into the HTML file;
Sending the HTML file with the script inserted to the client terminal;
When receiving display screen information from the client terminal, a recording step of recording the display screen information in a recording unit;
Generating link information to display screen information recorded in the recording means, generating a list screen for displaying the link information as a list, and publishing;
The screen information management method characterized by performing.   The screen information management method according to claim 1, wherein the script transmits, as the display screen information, the contents of a DOM tree displayed by a browser of the client terminal to the relay server.