Program, information processing device, and control method

Abstract

To improve user's convenience in using Web content.SOLUTION: A program is provided, which causes a computer to function as reception means for receiving an input of a first URL, and control means for performing acquisition processing of content associated with the first URL if the first URL does not match a second URL that has already inputted to the reception means when the reception means receives the input of the first URL, and executing control that does not perform the acquisition processing of the content associated with the first URL if the first URL matches the second URL.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present disclosure relates to a program, an information processing device, and a control method. [Background technology]

[0002] Some MFPs (Multi Function Peripherals, hereafter referred to as image forming apparatuses) equipped with scanner and printer functions are equipped with web browsers. Some web browsers are equipped with an input box (hereafter referred to as URL box) for inputting a destination URL (Uniform Resource Locator), and a button for accepting a page update instruction from a user. Even if the same connection URL is input in the URL box, the web browser may access the server every time to check for updates to the web content before displaying it.

[0003] Patent Document 1 discloses a method of storing Web content as a cache, and when an instruction to display the Web content is received again from a user, reading the Web content from the cache and displaying it. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2003-330789 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the method of Patent Document 1, if there is a cache of web content associated with the input connection URL, the web content is read from the cache and displayed. This causes a waiting time until the web content is displayed, which reduces user convenience. [Means for solving the problem]

[0006] A program according to one embodiment of the present disclosure is characterized in that it causes a computer to function as: a reception means for receiving an input of a first URL; and a control means for, if the first URL does not match a second URL that has already been input into the reception means when the reception means receives the input of the first URL, performing a process to acquire content linked to the first URL, and, if the first URL matches the second URL, executing control not to perform a process to acquire content linked to the first URL. Effect of the Invention

[0007] According to the present disclosure, it is possible to improve user convenience. [Brief description of the drawings]

[0008] [Figure 1] 1 is an overall view showing an example of an image processing system according to an embodiment. [Diagram 2] FIG. 1 is a block diagram showing an example of a configuration of an image forming apparatus 101 according to an embodiment. [Diagram 3] FIG. 2 is a diagram illustrating an example of a software configuration of an image forming apparatus 101 according to an embodiment. [Figure 4] 11 is a flowchart illustrating an example of processing executed by a Web browser 300 in the embodiment. [Diagram 5] FIG. 3 illustrates an example of a Web browser 300. [Figure 6] FIG. 6 illustrates an example of a URL information table 600. [Figure 7] 13 is a flowchart illustrating an example of a Web content acquisition process. [Figure 8] FIG. 13 illustrates an example of a request transmitted by a Web browser 300. [Figure 9] FIG. 13 is a diagram showing an example of a response received by the Web browser 300. [Figure 10]11 is a flowchart illustrating an example of processing executed by a Web browser 300 in the embodiment. [Figure 11] 11 is a flowchart illustrating an example of processing executed by a Web browser 300 in the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Preferred embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. Note that the following embodiments do not limit the present disclosure, and not all of the combinations of features described in the following embodiments are necessarily essential to the solutions of the present disclosure. Note that the same components will be described with the same reference numerals.

[0010] <First embodiment> In a case where an image forming apparatus having a Web browser is used, when a user inputs a connection URL into the URL box of the Web browser, the Web browser displays Web content associated with the URL. After this, it may happen that the user inputs the same connection URL again into the URL box. For example, after the user inputs a connection URL into the URL box, the user may accidentally touch the operation unit on which the Web browser is displayed. This may result in the user pressing the confirmation key on the opened soft keyboard and inputting the same connection URL. It is considered that the input of the same connection URL as the Web content already displayed into the URL box is an input error. On the other hand, as described above, a general Web browser is configured to access the server every time even if the same connection URL is input into the URL box, check the update of the Web content, and display it. Therefore, when a user inputs a connection URL into the URL box and then inputs the same connection URL again, there is a problem that the user has to wait a long time until the Web content is displayed. In addition, a similar problem occurs when reading out a cache of Web content that has already been acquired. Therefore, in this embodiment, a control is described in which a wait time is not generated until the Web content is redisplayed when the same URL as the URL already input into the URL box is input.

[0011] FIG. 1 is an overall view showing an example of an image processing system in the first embodiment. In the image processing system of the present disclosure, an image forming apparatus 101 and a server 102 are communicably connected via a network 110. The image forming apparatus 101 includes an installed Web browser 300. The Web browser 300 transmits a request to the server via the network 110 and receives a response to the request from the server to obtain Web content. The image forming apparatus 101 is a recording apparatus having a printing function of recording information on a print medium using a recording material, an apparatus further equipped with a reading apparatus for reading an image on a document and functioning as a copier, or a multifunction peripheral (MFP) with other functions added. However, various information processing apparatuses such as a personal computer (PC), a smartphone, a tablet terminal, and a digital camera may be applied as the image forming apparatus 101 of this embodiment.

[0012] 2 is a block diagram showing an example of the configuration of the image forming apparatus 101. The details of the configuration of the image forming apparatus 101 will be described with reference to FIG.

[0013] The image forming apparatus 101 includes a control unit 210, an operation unit 219, a printer 220, and a scanner 221. The control unit 210 includes a central processing unit (CPU) 211, a read only memory (ROM) 212, and a random access memory (RAM) 213. The control unit 210 includes a hard disk drive (HDD) 214, an operation unit interface (I / F) 215, a printer I / F 216, a scanner I / F 217, and a network I / F 218. The control unit 210 including the CPU 211 controls the operation of the entire image forming apparatus 101. The CPU 211 is a central processing unit that reads a control program stored in the ROM 212 and executes various control processes such as response reading control and request transmission control. The RAM 213 is a main memory of the CPU 211, and is used as a temporary storage area such as a work area.

[0014] The HDD 214 stores various data such as image content, image data, and various programs acquired from the server. The operation unit I / F 215 connects the operation unit 219 and the control unit 210. The operation unit 219 includes a liquid crystal display unit having a touch panel function, a keyboard having operation items such as a confirmation key, and the like. The keyboard may be a hard keyboard or a soft keyboard displayed on the liquid crystal display unit. Input data or control instructions received by the operation unit 219 are input to the control unit 210 via the operation unit I / F 215. The printer I / F 216 connects the printer 220 and the control unit 210. The printer 220 executes a process of forming image data on a recording medium (hereinafter referred to as printing). Image data to be printed by the printer 220 is transferred from the control unit 210 to the printer 220 via the printer I / F 216, and is printed by the printer 220. The scanner I / F 217 connects the scanner 221 and the control unit 210. The scanner 221 reads an image on a document to generate image data, and inputs the image data to the control unit 210 via the scanner I / F 217. The network I / F 218 connects the control unit 210 to the network 110.

[0015] Here, the acquisition of Web content will be described in detail. When a user specifies the URL address of a destination external device on Web browser 300 displayed on the liquid crystal display of operation unit 219, Web browser 300 transmits a request to the external device on network 110 via network I / F 218. When the external device is server 102, server 102, upon receiving the request, returns a response of the corresponding Web content to Web browser 300. The response of the Web content is generally written using HTML, CSS, JavaScript, etc. Web browser 300 converts the Web content acquired from server 102 into input fields, etc. (generally referred to as browser rendering processing, etc.), and displays the rendering result on the liquid crystal display.

[0016] Fig. 3 is a diagram showing an example of a software configuration of image forming apparatus 101. Web browser 300 will be described with reference to Fig. 3. Image forming apparatus 101 includes Web browser 300 as software realized by CPU 211 executing each control program stored in ROM 212 of image forming apparatus 101. Web browser 300 has a UI management unit 301, a URL recognition unit 302, a request transmission unit 303, a response reception unit 304, a response determination unit 305, and a response return unit 306.

[0017] The UI management unit 301 manages UIs such as a URL box, a reload button, a forward button, a back button, and a stop button provided in the Web browser 300, and judges whether the UIs have been operated by the user. The URL recognition unit 302 judges whether the URL designated by the user matches the URL of the currently displayed Web content. The URL recognition unit 302 also stores the URL designated by the user in a URL information table (to be described later) stored in the RAM 213 or the like, and reads the stored URL from the URL information table. The request transmission unit 303 transmits a request to the server 102. The response reception unit 304 receives a response of the Web content returned by the server 102. The response reception unit 304 also displays the rendering result of the received Web content on the liquid crystal display unit of the operation unit 219. The response determination unit 305 judges the content of the response of the Web content received by the response reception unit 304. The response return unit 306 returns the response of the Web content received by the response reception unit 304.

[0018] (Processing when entering URL in the URL box or pressing the reload button) FIG. 4 is a flowchart showing an example of a process executed by the Web browser 300 of the image forming apparatus 101 when the user inputs information into the URL box or presses the reload button. The process executed by the Web browser 300 in this embodiment will be described with reference to FIG. 4. In this embodiment, the image forming apparatus 101 is described as an MFP, but is not limited to this. The same applies to other embodiments. The process shown in FIG. 4 is realized by the CPU 211 of the image forming apparatus 101 reading a program stored in the ROM 212 or the like into the RAM 213 and executing it. Some or all of the functions of the steps in FIG. 4 may be realized by hardware such as an ASIC or an electronic circuit. The symbol "S" in the description of each process means a step in the flowchart (the same applies to the flowcharts in the following specification). The process shown in FIG. 4 starts when the Web browser 300 is started from a menu screen (not shown) displayed when the power of the image forming apparatus 101 is turned on.

[0019] In S401, the CPU 211 uses the UI management unit 301 to accept input from the user to the Web browser 300. Specifically, the CPU 211 displays a screen of the Web browser 300 as shown in FIG. 5(a) and accepts input from the user. FIG. 5(a) is a diagram showing an example of a screen displayed when the Web browser 300 is started. The screen of the Web browser 300 in FIG. 5(a) has a reload button 501 and a URL box 502. The reload button 501 functions as an update acceptance unit that accepts an instruction to update resources of Web content. The URL box 502 functions as an acceptance unit that accepts an input of a URL linked to a Web page desired by the user. Returning to FIG. 4, the CPU 211 then proceeds to the process of S402.

[0020] In S402, the CPU 211 uses the UI management unit 301 to determine whether or not there has been an input from the user to the Web browser 300. If the CPU 211 determines that there has been an input from the user (Yes), the process proceeds to S403, and if the CPU 211 determines that there has been an input from the user (No), the process proceeds to S401. That is, the CPU 211 continues the process of S402 until there is an input from the user. In S403, the CPU 211 uses the UI management unit 301 to determine whether or not there has been an input from the user to the URL box 502 when determining that there has been an input in S402. For example, the CPU 211 may determine that there has been an input to the URL box 502 in response to a URL being input to the URL box 502 and a confirmation key being pressed to confirm the input. Also, a keyboard is displayed on the operation unit when the user performs a pressing operation on the URL box 502 in which a URL has already been input. Then, the CPU 211 may determine that there has been an input to the URL box 502 when the user presses the confirmation key on the displayed keyboard. Furthermore, CPU 211 may determine that a URL has been input by supplementing the scheme portion even if the scheme portion of the URL (such as http: / / ) has not been input into URL box 502. If CPU 211 determines that there has been input from the user into URL box 502 (Yes), it proceeds to processing of S404, and if it determines that there has not been input (No), it proceeds to processing of S405.

[0021] In S404, CPU 211 uses URL recognition unit 302 to read out an already-input URL from a URL information table stored in HDD 214, RAM 213, etc. Here, the already-input URL is a URL that was input into the URL box immediately before the URL input in S402 and is managed in the URL information table. For example, CPU 211 reads out a URL from URL information table 600 as shown in FIG.

[0022] FIG. 6 is a diagram showing an example of a URL information table. In the URL information table 600, the URLs inputted to the URL box 502 are managed by associating the URLs with the URL information IDs. The management method of the inputted URLs is not limited to this. In other words, as long as the CPU 211 can determine whether the inputted URL matches the already inputted URL, the method of storing and managing the URL is not limited. Returning to FIG. 4, the CPU 211 uses the URL recognition unit 302 to determine whether the URL inputted to the URL box by the user in S403 matches the already inputted URL. The CPU 211 may determine whether the URL matches the already inputted URL regardless of whether the scheme part (such as http: / / ) of the URL is inputted. Specifically, when "http: / / www.aaa.bbb" has already been inputted to the URL box, even if "www.aaa.bbb" is inputted thereafter, the CPU 211 may determine that the inputted URL matches the already inputted URL. If CPU211 determines that the input URL matches a URL that has already been input (Yes), it ends this process, and if it determines that it does not match (No), it proceeds to the process of S406. When Web browser 300 is started, URL information table 600 is empty. That is, if there is no URL input before the input of the URL accepted in S402 after Web browser 300 is started, CPU211 proceeds to the process of S406. When a page to be displayed when Web browser 300 is started is set, the URL associated with the set page may be saved in URL information table 600. In this case, CPU211 determines whether the URL associated with the set page matches the URL input in the URL box.

[0023] In S405, the CPU 211 uses the UI management unit 301 to determine whether or not the reload button 501 has been pressed by the user. If the CPU 211 determines that the reload button 501 has been pressed by the user (Yes), the process proceeds to S406, and if the CPU 211 determines that the reload button 501 has not been pressed by the user (No), the process ends. In S406, the CPU 211 uses the request transmission unit 303, the response reception unit 304, and the response determination unit 305 to perform Web content acquisition processing, and ends the process. In this embodiment, even if the process shown in FIG. 4 ends, the process continues unless the image forming apparatus 101 is powered off. In other words, after the process ends, the CPU 211 returns to S401 again (not shown) and repeats the process. The same applies to the processes in FIGS. 10 and 11 described later.

[0024] (Web content acquisition process) 7 is a flowchart showing an example of a Web content acquisition process executed by the Web browser 300 in S406. A process in which the Web browser 300 of the image forming apparatus 101 in this embodiment transmits a request to the server 102 of a specified URL and acquires Web content from the server 102 will be described with reference to FIG.

[0025] In S701, the CPU 211 uses the request sending unit 303 to send a request to confirm the update of the main resource to the server 102 of the URL input in S403. After that, the CPU 211 proceeds to the process of S702. In S702, the CPU 211 uses the response receiving unit 304 to determine whether or not a response confirming the update of the main resource has been received from the server 102. If the CPU 211 determines that a response confirming the update of the main resource has been received from the server 102 (Yes), the process proceeds to the process of S703, and if the CPU 211 determines that a response confirming the update of the main resource has not been received (No), the process proceeds to the process of S702. In other words, the CPU 211 continues the process of S702 until a response confirming the update of the main resource is received.

[0026] In S703, the CPU 211 uses the response determination unit 305 to determine whether or not the response received from the server 102 in S702 was a request for updating the main resource. If the CPU 211 determines that the response received from the server 102 was a request for updating the main resource (Yes), the CPU 211 proceeds to the process of S704, and if the CPU 211 determines that the response was not a request for updating the main resource (No), the CPU 211 ends this process. Note that if the same URL is not input before the input of the URL in S402, the CPU 211 does not need to execute the processes from S701 to S703. Here, the confirmation of the update of the main resource is a process of confirming whether or not the cached main resource needs to be updated when the main resource of the already input URL is cached. In other words, if there is no cached main resource, the process from S701 to S703 does not need to be executed.

[0027] In S704, the CPU 211 uses the request transmission unit 303 to transmit a request to acquire the main resource to the server 102. After that, the CPU 211 proceeds to the process of S705. In S705, the CPU 211 uses the response reception unit 304 to determine whether or not a response to the main resource acquisition has been received from the server 102. If the CPU 211 determines that a response to the main resource acquisition has been received from the server 102 (Yes), the process proceeds to the process of S706, and if the CPU 211 determines that a response to the main resource acquisition has not been received (No), the process proceeds to the process of S705. That is, the CPU 211 continues the process of S705 until a response to the main resource acquisition is received. In S706, the CPU 211 uses the response reception unit 304 to store the main resource received in S705 in the HDD 214, the RAM 213, or the like. After that, the CPU 211 proceeds to the process of S707.

[0028] In S707, the CPU 211 uses the request sending unit 303 to send a request to the server 102 to confirm the update of the sub-resource. After that, the CPU 211 proceeds to the process of S708. In S708, the CPU 211 uses the response receiving unit 304 to determine whether or not a response confirming the update of the sub-resource has been received from the server 102. If the CPU 211 determines that a response confirming the update of the sub-resource has been received from the server 102 (Yes), the CPU 211 proceeds to the process of S709, and if the CPU 211 determines that a response confirming the update of the sub-resource has not been received (No), the CPU 211 proceeds to the process of S708. In other words, the CPU 211 continues the process of S708 until a response confirming the update of the sub-resource is received.

[0029] In S709, the CPU 211 uses the response determination unit 305 to determine whether or not the response received from the server 102 in S708 was a request for updating the sub-resources. If the CPU 211 determines that the response received from the server 102 was a request for updating the sub-resources (Yes), the process proceeds to S710, and if the CPU 211 determines that the response was not a request for updating the sub-resources (No), the process ends. Note that, for the same reason as in the above-described processes of S701 to S703, if there are no cached sub-resources, the processes of S707 to S709 do not need to be executed.

[0030] In S710, the CPU 211 uses the request transmission unit 303 to transmit a request to acquire a sub-resource to the server 102. After that, the CPU 211 proceeds to the process of S711. In S711, the CPU 211 uses the response reception unit 304 to determine whether or not a response to the sub-resource acquisition has been received from the server 102. If the CPU 211 determines that a response to the sub-resource acquisition has been received from the server 102 (Yes), the process proceeds to the process of S712, and if the CPU 211 determines that a response to the sub-resource acquisition has not been received (No), the process proceeds to the process of S711. That is, the CPU 211 continues the process of S711 until a response to the sub-resource acquisition is received. In S712, the CPU 211 uses the response reception unit 304 to store the sub-resource received in S711 in the HDD 214, the RAM 213, or the like. After that, the CPU 211 proceeds to the process of S713.

[0031] In S713, the CPU 211 uses the response receiving unit 304 to determine whether or not all the sub-resources have been received in S711. If the CPU 211 determines that all the sub-resources have been received (Yes), the process proceeds to S714, and if the CPU 211 determines that all the sub-resources have not been received (No), the process proceeds to S710. That is, the CPU 211 continues the processes from S710 to S713 until all the sub-resources have been received. In S714, the CPU 211 uses the UI management unit 301 to read out the main resource saved in S706 and the sub-resource saved in S712 from the HDD 214 or the RAM 213. Then, the CPU 211 uses the UI management unit 301 to display the rendering result on the display of the operation unit 219. After that, the CPU 211 proceeds to the process of S715. In S715, the CPU 211 uses the URL recognition unit 302 to store the URL input in S402 in the URL information table 600 stored in the HDD 214, the RAM 213, or the like, and ends this process.

[0032] (Application example 1) 4 and 7, after a user inputs a URL into the URL box, Web browser 300 accesses server 102 of the input URL. Then, after Web browser 300 acquires Web content, a case will be described in which the same URL is input again by the user.

[0033] (First processing in application example 1) The first process executed by the Web browser will be described with reference to Figures 4 and 7. At the start of this process, the screen of the Web browser 300 is in the state shown in Figure 5(a). The URL information table 600 in Figure 6 is empty and has nothing entered. The URL of the server 102 is "http: / / www.aaa.bbb". First, with reference to Figure 4, this process is started when the Web browser 300 is started, and the CPU 211 executes the process of S401.

[0034] In S401, CPU 211 uses UI management unit 301 to accept input from the user to Web browser 300. At this time, the screen state of Web browser 300 accepts input from the user with URL box 502 left blank, as shown in Fig. 5(a). Then, CPU 211 proceeds to the process of S402.

[0035] In S402, the CPU 211 uses the UI management unit 301 to determine whether or not there has been an input from the user to the Web browser 300. It is assumed that the user inputs "http: / / www.aaa.bbb", which is the URL of the server 102, into the URL box 502. In this case, since the user inputs a URL (first URL) into the URL box 502 in FIG. 5(a), the CPU 211 proceeds to processing of S403. In S403, the CPU 211 uses the UI management unit 301 to determine whether or not there has been an input from the user into the URL box when detecting the input in S402. As described above, since the user inputs a URL into the URL box 502 in FIG. 5(a), the CPU 211 proceeds to processing of S404.

[0036] In S404, CPU 211 uses URL recognition unit 302 to read out an already-input URL from URL information table 600 stored in HDD 214 or RAM 213. Here, URL information table 600 is empty, i.e., nothing is stored therein, so CPU 211 reads out an empty URL as an already-input URL (second URL). Then, CPU 211 uses URL recognition unit 302 to determine whether or not the URL ("http: / / www.aaa.bbb") input by the user into the URL box in S402 matches the already-input URL (empty URL). Here, CPU 211 determines that the URLs do not match, and proceeds to processing in S406. In S406, CPU 211 uses request transmission unit 303, response reception unit 304, and response determination unit 305 to perform Web content acquisition processing, and ends this processing.

[0037] Next, the details of the Web content acquisition process will be described with reference to FIG. 7. In S701, the CPU 211 uses the request transmission unit 303 to transmit a request for confirming the update of the main resource to the server 102 of the URL input in S402. Specifically, the CPU 211 transmits a request for confirming the update of the main resource to the server 102 linked to the URL "http: / / www.aaa.bbb" input in S402, as shown in FIG. 8. FIG. 8 is a diagram showing an example of a request transmitted by the Web browser 300. The request in FIG. 8 includes a request header 801. The request header 801 describes information such as the type of data that can be processed on the image forming apparatus 101 side. Returning to FIG. 7, the CPU 211 then proceeds to the process of S702.

[0038] In S702, the CPU 211 uses the response receiving unit 304 to determine whether or not a response has been received from the server 102 to confirm the update of the main resource. Here, it is assumed that the CPU 211 has determined that a response has been received from the server 102 to confirm the update of the main resource, and the process proceeds to S703. In S703, the CPU 211 uses the response determining unit 305 to determine whether or not the response received from the server 102 in S702 was a request for updating the main resource. Here, it is assumed that the CPU 211 has determined that the response received from the server 102 was a request for updating the main resource, and the process proceeds to S704. In S704, the CPU 211 uses the request transmitting unit 303 to transmit a request to the server 102 to acquire the main resource. Thereafter, the CPU 211 proceeds to the process of S705.

[0039] In S705, the CPU 211 uses the response receiving unit 304 to determine whether or not a response to acquire the main resource has been received from the server 102. Specifically, the CPU 211 receives a response as shown in FIG. 9A. FIG. 9A is a diagram showing an example of a response received by the Web browser 300. The response in FIG. 9A has a response header 901 and a response body 902. The response header 901 describes the result of the request sent in S704, the date and time when the server 102 returned the response, and the like. The response header 901 may also describe information indicating the last update date and time of the resource, which is used to check the next update of the resource, or an ETag, and the like. The main resource is described in the response body 902. Here, the CPU 211 determines that a response to acquire the main resource has been received from the server 102, and proceeds to the process of S706.

[0040] In S706, the CPU 211 uses the response receiving unit 304 to store the main resource received in S705 in the HDD 214, the RAM 213, or the like. After that, the CPU 211 proceeds to the process of S707. In S707, the CPU 211 uses the request sending unit 303 to send a request to the server 102 to confirm the update of the sub-resource. After that, the CPU 211 proceeds to the process of S708. In S708, the CPU 211 uses the response receiving unit 304 to determine whether or not a response confirming the update of the sub-resource has been received from the server 102. Here, the CPU 211 proceeds to the process of S709 assuming that a response confirming the update of the sub-resource has been received from the server 102.

[0041] In S709, the CPU 211 uses the response determination unit 305 to determine whether or not the response received from the server 102 in S708 was a request to update the sub-resources. Here, the CPU 211 determines that the response received from the server 102 was a request to update the sub-resources, and proceeds to the process of S710. In S710, the CPU 211 uses the request transmission unit 303 to transmit a request to the server 102 to acquire the sub-resources. After that, the CPU 211 proceeds to the process of S711.

[0042] In S711, the CPU 211 uses the response receiving unit 304 to determine whether or not a response to the sub-resource acquisition from the server 102 has been received. Here, the CPU 211 determines that a response to the sub-resource acquisition from the server 102 has been received, and proceeds to processing of S712. Note that the response to the sub-resource acquisition may include information indicating the last update date and time of the resource, or an ETag, which is used to check the next update of the resource. In S712, the CPU 211 uses the response receiving unit 304 to store the sub-resource received in S711 in the HDD 214, the RAM 213, or the like. Thereafter, the CPU 211 proceeds to processing of S713. In S713, the CPU 211 uses the response receiving unit 304 to determine whether or not all the sub-resources have been received in S711. Here, the CPU 211 determines that all the sub-resources have been received, and proceeds to processing of S714.

[0043] In S714, the CPU 211 uses the UI management unit 301 to read out the main resource saved in S706 and the sub-resource saved in S712 from the HDD 214, the RAM 213, or the like. In addition, the CPU 211 uses the UI management unit 301 to display the rendering result on the display of the operation unit 219. Here, the CPU 211 displays a screen of the rendering result as shown in FIG. 5(b) on the display of the operation unit 219. FIG. 5(b) is a diagram showing an example of the Web browser 300 after a URL is input and a Web page is displayed. Returning to FIG. 4, the CPU 211 then proceeds to the process of S715. In S715, the CPU 211 uses the URL recognition unit 302 to save the URL "http: / / www.aaa.bbb" input in S402 in the URL information table 600 saved in the HDD 214, the RAM 213, or the like, and ends this process.

[0044] (Second processing in application example 1) Next, with the URL "http: / / www.aaa.bbb" input in URL box 502 on the display screen of Web browser 300, CPU 211 starts the process of Fig. 4 again. In S401, CPU 211 uses UI management unit 301 to accept input from the user to Web browser 300. That is, as shown in Fig. 5(b), with the input "http: / / www.aaa.bbb" displayed in URL box 502, CPU 211 accepts input from the user. Thereafter, CPU 211 proceeds to the process of S402.

[0045] In S402, the CPU 211 uses the UI management unit 301 to determine whether or not there has been an input from the user to the Web browser 300. At this time, it is assumed that the user inputs "http: / / www.aaa.bbb", which is the same URL as the URL already displayed, into the URL box 502. Then, as shown in the URL box 502 in FIG. 5B, "http: / / www.aaa.bbb" is displayed in the URL box. Since the user inputs a URL (first URL) into the URL box 502 in FIG. 5B, the CPU 211 proceeds to processing of S403. In S403, the CPU 211 uses the UI management unit 301 to determine whether or not there has been an input into the URL box from the user when the input is detected in the immediately preceding S402. As described above, since the user inputs a URL into the URL box 502 in FIG. 5B, the CPU 211 proceeds to processing of S404.

[0046] In S404, CPU 211 uses URL recognition unit 302 to read out an already input URL (second URL) from URL information table 600 stored in HDD 214 or RAM 213. Here, URL "http: / / www.aaa.bbb" is read out from URL information table 600 as an already input URL. Then, CPU 211 uses URL recognition unit 302 to determine whether the URL input in the URL box ("http: / / www.aaa.bbb") matches the already input URL ("http: / / www.aaa.bbb"). Here, CPU 211 determines that the URLs match, and ends the process. That is, in the second process in application example 1, the URL input by the user is the same as the already input URL, so CPU 211 does not perform the Web content acquisition process in S406.

[0047] (Application example 2) As an application example of the processes in FIGS. 4 and 7, a case will be described in which the user accesses server 102 at the URL specified in URL box 502, acquires Web content, and then presses reload button 501.

[0048] (First processing in application example 2) This process starts in the same state as the first process in application example 1. Since this process is the same as the first process in application example 1, the description of the flowcharts in Figs. 4 and 7 will be omitted.

[0049] (Second processing in application example 2) This process starts in the same state as the second process in application example 1. In S401, CPU 211 uses UI management unit 301 to accept input from the user to Web browser 300. At this time, the screen of Web browser 300 is in a state in which URL "http: / / www.aaa.bbb" that has already been input is displayed in URL box 502 as shown in FIG. 5B. In S402, CPU 211 uses UI management unit 301 to determine whether or not there has been input from the user to Web browser 300. At this time, it is assumed that the user presses reload button 501 in FIG. 5B. Then, since the user has pressed reload button 501, CPU 211 proceeds to the process of S403.

[0050] In S403, the CPU 211 uses the UI management unit 301 to determine whether or not the user has input to the URL box when the input is detected in the immediately preceding S402. As described above, the reload button 501 in FIG. 5B has been pressed by the user, so the CPU 211 determines that there has been no input to the URL box 502, and proceeds to processing of S405. In S405, the CPU 211 uses the UI management unit 301 to determine whether or not the reload button has been pressed by the user when the input is detected in S402. As described above, the reload button 501 in FIG. 5B has been pressed by the user, so the CPU 211 proceeds to processing of S406. In S406, the CPU 211 uses the request transmission unit 303, the response reception unit 304, and the response determination unit 305 to perform Web content acquisition processing, and ends this processing.

[0051] 7 in the second processing in application example 2 is similar to the first processing in application example 1, and therefore will not be described. That is, in the second processing in application example 2, when the reload button 501 is pressed by the user, the CPU 211 performs the Web content acquisition process of S406 regardless of the URL that has already been input.

[0052] As described in the above application example 1, when the user inputs a URL in URL box 502 in Fig. 5(a), the Web browser displays the Web content. If the user subsequently inputs the same URL in URL box 502 in Fig. 5(b), the Web browser does not access the server, does not read from the cache, and continues to display the current Web content. Also, as described in the first processing in application example 1, if the URL input by the user is different from the URL of the currently displayed Web content, the Web browser accesses the server to check whether the Web content has been updated. As described in the above application example 2, even if the user presses reload button 501, the Web browser accesses the server to check whether the Web content has been updated.

[0053] According to this embodiment, if a user inputs a URL into the URL box and the web content is displayed, and then inputs the same URL as the URL already input into the URL box, the web browser does not access the server or read from the cache. This eliminates the waiting time until the content is redisplayed, improving user convenience. In addition, the web content can be displayed appropriately even if a user inputs a URL different from the one already input, or if the reload button is pressed to instruct updating of the web content resources.

[0054] <Second embodiment> A case where the Web browser 300 acquires Web content from the server 102 and the Web content is designated as cache-prohibited will be described with reference to Fig. 10 while describing the differences from the first embodiment. Note that, unless otherwise specified, in this embodiment, the same block diagrams and processes in the same flowcharts as those in the first embodiment will be described with the same reference numerals.

[0055] (Processing when entering URL in the URL box or pressing the reload button) Fig. 10 is a flowchart showing an example of processing executed by the Web browser 300 of the image forming apparatus 101 when the user inputs information into the URL box or presses the reload button. The processing executed by the Web browser 300 in this embodiment will be described with reference to Fig. 10. As in the first embodiment, the processing in Fig. 10 starts when the Web browser 300 is started from a menu screen (not shown) that is displayed when the image forming apparatus 101 is powered on, and ends when the image forming apparatus 101 is powered off. Note that the processing from S401 to S406 is the same as in the first embodiment, and therefore description thereof will be omitted.

[0056] In S1001, the CPU 211 determines whether or not the Web content received in S406 has a cache prohibition designation, using the response determination unit 305. If the CPU 211 determines that the Web content received in S406 has a cache prohibition designation (Yes), it proceeds to the process of S406, and if it determines that the Web content has not had a cache prohibition designation (No), it ends this process.

[0057] (Application example 3) 10 and 7, the Web browser 300 accesses the server 102 of the URL specified by the user in the URL box, and acquires the Web content. If the Web content is designated as being cache-prohibited, the following will describe the case where the user inputs the same URL again.

[0058] In this application example, the URL information table 600 in Fig. 6 is assumed to be empty. Also, in this application example, the screen state of the Web browser 300 is assumed to be the state immediately after the Web browser 300 is started, that is, the state shown in Fig. 5(a). Also, in this application example, the URL of the server 102 is assumed to be "http: / / www.aaa.bbb".

[0059] (First processing in application example 3) The first processing in application example 3 is similar to the first processing in application example 1 described above, and therefore the description will be omitted. That is, assume that the user inputs URL "http: / / www.aaa.bbb" into URL box 502 in Fig. 5(a), and CPU 211 proceeds to Web content acquisition processing in S406. The Web content acquisition processing in S406 will be described with reference to Fig. 7, but since S701 to S704 and S706 to S715 are similar to the first processing in application example 1 described above, the description will be omitted.

[0060] In S705, the CPU 211 uses the response receiving unit 304 to determine whether or not a response to the main resource acquisition has been received from the server 102. In this case, the CPU 211 determines that a response such as that shown in FIG. 9B has been received as a response to the main resource acquisition from the server 102, and proceeds to the process of S706. FIG. 9B is a diagram showing an example of a response received by the Web browser 300. The response header 911 in FIG. 9B contains the following: <meta http-equiv="”Cache-Control"" content="”no-cache""> This setting prohibits caching of this Web content.

[0061] (Second processing in application example 3) Next, with URL "http: / / www.aaa.bbb" entered in URL box 502 on the display screen of Web browser 300, CPU 211 starts the process of Fig. 10 again. In S401, CPU 211 uses UI management unit 301 to accept input from the user to Web browser 300. That is, as shown in Fig. 5(b), with "http: / / www.aaa.bbb" entered in URL box 502 displayed, CPU 211 accepts input from the user. Thereafter, CPU 211 proceeds to the process of S402.

[0062] In S402, the CPU 211 uses the UI management unit 301 to determine whether or not there has been an input from the user to the Web browser 300. At this time, it is assumed that the user inputs "http: / / www.aaa.bbb", which is the same URL as the URL already displayed, into the URL box 502. Then, as shown in the URL box 502 of FIG. 5B, "http: / / www.aaa.bbb" is displayed in the URL box. As described above, since the user inputs a URL into the URL box 502 of FIG. 5B, the CPU 211 proceeds to processing of S403. In S403, the CPU 211 uses the UI management unit 301 to determine whether or not there has been an input into the URL box from the user when the input is detected in the immediately preceding S402. As described above, since the user inputs a URL into the URL box 502 of FIG. 5B, the CPU 211 proceeds to processing of S404.

[0063] In S404, CPU 211 uses URL recognition unit 302 to read out an already-entered URL from URL information table 600 stored in HDD 214, RAM 213, or the like. Here, URL "http: / / www.aaa.bbb" is read out from URL information table 600 as an already-entered URL. Then, CPU 211 uses URL recognition unit 302 to determine whether the URL ("http: / / www.aaa.bbb") entered by the user in the URL box matches the already-entered URL ("http: / / www.aaa.bbb"). Here, CPU 211 determines that the URLs match, and proceeds to the processing of S1001.

[0064] In S1001, the CPU 211 uses the response determination unit 305 to determine whether or not the Web content of FIG. 9B received in S705 has a cache prohibition designation. <meta http-equiv="”Cache-Control"" content="”no-cache"">", which prohibits caching of the Web content. Therefore, CPU 211 determines that the Web content has a cache prohibition designation, and proceeds to processing of S406. In S406, CPU 211 performs Web content acquisition processing using request sending unit 303, response receiving unit 304, and response determination unit 305. CPU 211 then terminates this processing. The Web content acquisition processing of Figure 10 is similar to the first processing in the above-mentioned application example 3, and so description is omitted. In the second processing in application example 3, if the Web content has a cache prohibition designation, Web browser 300 performs the Web content acquisition processing of S406.

[0065] In the case where the Web content is designated as cache-prohibited, the Web browser accesses the server and checks whether the Web content has been updated. In the first embodiment, even if the Web content is designated as cache-prohibited, when the same URL is entered in the URL box, the Web browser 300 displays the current Web content without accessing the server or reading from the cache. In other words, in the first embodiment, when the Web content is designated as cache-prohibited, the Web browser 300 performs a process equivalent to the process of displaying the Web content from the cache, so there may be cases where the above-mentioned Web content specifications are not met. According to this embodiment, when the Web content is designated as cache-prohibited, the Web browser accesses the server and checks whether the Web content has been updated. This makes it possible to realize the Web browser's processing that is more suitable for the above-mentioned Web content specifications.

[0066] <Third embodiment> A case where the Web browser 300 acquires Web content from the server 102, is left for a certain period of time, and then the same URL is entered into the URL box by the user will be described with reference to Fig. 11, while describing the differences from the second embodiment. Unless otherwise specified, in this embodiment, block diagrams with the same numbers as in the second embodiment and processes of the same flowcharts are described with the same reference numerals.

[0067] (Processing when entering URL in the URL box or pressing the reload button) Fig. 11 is a flowchart showing an example of processing executed by the Web browser 300 of the image forming apparatus 101 when the user inputs information into the URL box or presses the reload button. The processing executed by the Web browser 300 in this embodiment will be described with reference to Fig. 11. As in the second embodiment, the processing in Fig. 11 starts when the Web browser 300 is started from a menu screen (not shown) that is displayed when the image forming apparatus 101 is powered on, and ends when the image forming apparatus 101 is powered off. Note that the processing from S401 to S406 and S1001 is the same as in the second embodiment, and therefore description thereof will be omitted.

[0068] In S1101, CPU 211 uses UI management unit 301 to set a timer for measuring the time for which input to the URL box by the user is accepted. After that, CPU 211 proceeds to the process of S401. In S1102, CPU 211 uses UI management unit 301 to measure the time from when input to the URL box from the user is accepted until the next time input to the URL box from the user is accepted, using the timer set in S1101. Then, CPU 211 uses UI management unit 301 to determine whether the measured time is equal to or greater than an arbitrary threshold value (first threshold value). That is, if the measured time is equal to or greater than the arbitrary threshold value, CPU 211 determines that a timeout has occurred (Yes) and proceeds to the process of S406, and if it determines that this is not the case (No), proceeds to the process of S404.

[0069] (Application example 4) 11 and 7, the Web browser 300 accesses the server 102 of the URL specified by the user in the URL box, and acquires the Web content. Then, after the browser is left for a certain period of time, the same URL is input by the user in the URL box.

[0070] In this application example, the URL information table 600 in Fig. 6 is assumed to be empty. Also, in this application example, the screen state of the Web browser 300 is assumed to be the state immediately after the Web browser 300 is started, that is, the state shown in Fig. 5(a). Also, in this application example, the URL of the server 102 is assumed to be "http: / / www.aaa.bbb".

[0071] (First processing in Application Example 4) The first processing in application example 4 will be described with reference to Fig. 11. In S1101, the CPU 211 uses the UI management unit 301 to set a timer for measuring the time when an input to the URL box by the user is accepted. After that, the CPU 211 proceeds to the processing of S401.

[0072] In S401, CPU 211 uses UI management unit 301 to accept input from the user to Web browser 300. At this time, the screen state of Web browser 300 accepts input from the user with URL box 502 left blank, as shown in Fig. 5(a). After this, CPU 211 proceeds to the process of S402.

[0073] In S402, the CPU 211, using the UI management unit 301, determines whether or not there has been an input from the user to the Web browser 300. At this time, it is assumed that the user inputs "http: / / www.aaa.bbb", which is the URL of the server 102, into the URL box 502. Since the user inputs a URL into the URL box 502 in Fig. 5(a), the CPU 211 proceeds to the process of S403.

[0074] In S403, when the CPU 211 detects an input in S402, it determines whether or not there has been an input from the user to the URL box, using the UI management unit 301. As described above, since the user has input a URL to the URL box 502 in Fig. 5(a), the CPU 211 transitions to the process of S1102. Here, the CPU 211 may save the time from when the timer is set in S1101 until the input from the user to the URL box is accepted.

[0075] In S1102, CPU 211 uses UI management unit 301 to measure the time from when input to the URL box from the user is accepted to when the next input to the URL box from the user is accepted, using the timer set in S1101. Here, URL box 502 is blank before the URL is entered in S402. That is, CPU 211 has not accepted the second URL entry required to measure the time. In this case, CPU 211 proceeds to the process of S404 without measuring the time.

[0076] In S404, the CPU 211 uses the URL recognition unit 302 to read out already-input URLs from the URL information table 600 stored in the HDD 214 or the RAM 213. Here, since the URL information table 600 is empty and nothing is stored therein, an empty URL is read out as an already-input URL. Then, the CPU 211 uses the URL recognition unit 302 to determine whether the URL ("http: / / www.aaa.bbb") input by the user in the URL box in S402 matches the already-input URL (empty URL). Here, the CPU 211 determines that the URLs do not match, and proceeds to the process of S406. In S406, the CPU 211 uses the request transmission unit 303, the response reception unit 304, and the response determination unit 305 to perform a Web content acquisition process, and ends this process. Note that the Web content acquisition process is the same as the first process in the application example 1, and therefore a description thereof will be omitted.

[0077] (Second processing in application example 4) Next, with the URL "http: / / www.aaa.bbb" entered in URL box 502 on the display screen of Web browser 300, CPU 211 starts the process of Fig. 11 again. In S1101, CPU 211 uses UI management unit 301 to set a timer for measuring the time for accepting input into the URL box by the user. Then, CPU 211 proceeds to the process of S401.

[0078] In S401, the CPU 211 uses the UI management unit 301 to accept input from the user to the Web browser 300. That is, as shown in Fig. 5B, the CPU 211 accepts input from the user in a state in which "http: / / www.aaa.bbb" entered in the URL box 502 is displayed. Thereafter, the CPU 211 proceeds to the process of S402.

[0079] In S402, the CPU 211, using the UI management unit 301, determines whether or not there has been an input from the user to the Web browser 300. At this time, it is assumed that the user inputs "http: / / www.aaa.bbb", which is the URL of the server 102, into the URL box 502. Since the user inputs a URL into the URL box 502 in Fig. 5(b), the CPU 211 proceeds to the process of S403.

[0080] In S403, the CPU 211 uses the UI management unit 301 to determine whether or not there was an input from the user to the URL box when the input was detected in the immediately preceding S402. As described above, since the user input a URL to the URL box 502 in Fig. 5(b), the CPU 211 proceeds to the process of S1102. Here, the CPU 211 may save the time from setting the timer in the second S1101 to accepting the input from the user to the URL box in the second S402.

[0081] In S1102, the CPU 211 uses the UI management unit 301 to measure the time from when the URL box input from the user is received to when the next URL box input from the user is received, using the timer set in S1102. For example, the CPU 211 may measure the time from the timer time information saved when the URL input to the URL box is detected in S403 for the first time and the timer time information saved in S403 for the second time. Note that the method of using the timer and the method of measuring the time using the timer are not limited to the above, as long as the time from when the URL box input from the user is received to when the next URL box input from the user is received can be measured. Here, the CPU 211 uses the UI management unit 301 to determine that the measured time is equal to or greater than an arbitrary threshold, that is, a timeout has occurred, and proceeds to the process of S406. In S406, the CPU 211 uses the request transmission unit 303, the response reception unit 304, and the response determination unit 305 to perform a Web content acquisition process, and ends this process. The Web content acquisition process in S406 in FIG. 11 is similar to the first process in the above-described application example 1, and therefore a description thereof will be omitted.

[0082] In the first and second embodiments, for example, if a URL is left in the URL box for a certain period of time and the same URL is then entered in the URL box, the Web content may not be acquired. In other words, in this case, the first and second embodiments do not access the server, so the displayed Web content may become outdated and updated Web content may not be displayed.

[0083] According to this embodiment, the web browser measures the time from when it accepts an input to the URL box from the user until the next time it accepts an input to the URL box from the user, and if a certain period of time has passed, it determines that a timeout has occurred. The web browser then accesses the server and checks whether the web content has been updated. This reduces the risk that the displayed web content will become outdated, and makes it possible to display updated web content.

[0084] <Other embodiments> The present disclosure can also be realized by a process in which a program for implementing one or more functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. It can also be realized by a circuit (e.g., ASIC) that implements one or more functions.

[0085] The disclosure of the present embodiment includes configurations typified by the following program examples, information processing device examples, and control method examples.

[0086] <Configuration 1> Computer, A receiving means for receiving an input of a first URL; performing a process of acquiring content associated with the first URL when the first URL does not match a second URL already input to the receiving means when the receiving means receives the input of the first URL; a control means for executing control not to perform an acquisition process of the content associated with the first URL when the first URL matches the second URL; A program characterized by causing the program to function as a

[0087] <Configuration 2> the control means executes control to perform an acquisition process of the content associated with the second URL; The program described in configuration 1, characterized in that, when the first URL matches the second URL, the control means executes control to not load the cache of content linked to the second URL.

[0088] <Configuration 3> The program described in configuration 1 or 2, characterized in that, when the first URL matches the second URL, the control means executes control not to access a server linked to the first URL.

[0089] <Configuration 4> update receiving means for receiving an instruction to update the content linked to the first URL; Functioning as a The program according to any one of configurations 1 to 3, characterized in that when the update receiving means receives the instruction, the control means executes control to perform an acquisition process of content linked to the first URL.

[0090] <Component 5> The program according to configuration 2, characterized in that, when the content linked to the second URL has a cache prohibition designation, the control means executes control to perform an acquisition process of the content linked to the first URL.

[0091] <Component 6> a means for setting a timer for acquiring a time when the computer receives input of the first and second URLs; Functioning as a The program described in any one of configurations 1 to 5, characterized in that when the time between accepting input of the second URL and accepting input of the first URL, acquired by a timer set in the means, is equal to or longer than a first threshold, the control means executes control to perform an acquisition process of content linked to the first URL.

[0092] <Component 7> The program described in any one of configurations 1 to 6, characterized in that the receiving means receives input of the first URL in response to the first URL being entered into a URL box and an operation item for confirming the input being pressed.

[0093] <Component 8> The program according to any one of configurations 1 to 7, wherein the program is installed in an image forming apparatus.

[0094] <Component 9> A receiving means for receiving an input of a first URL; performing a process of acquiring content associated with the first URL when the first URL does not match a second URL already input to the receiving means when the receiving means receives the input of the first URL; a control means for executing control not to perform an acquisition process of the content associated with the first URL when the first URL matches the second URL; An information processing device comprising:

[0095] <Component 10> a receiving step of receiving an input of a first URL; performing a process of acquiring content associated with the first URL when the first URL does not match a second URL already input to the receiving means when the receiving means receives the input of the first URL; a control step of executing a control not to perform an acquisition process of the content associated with the first URL when the first URL matches the second URL; 13. A method for controlling an information processing apparatus comprising the steps of: [Explanation of symbols]

[0096] 101 Image forming device 211 CPU 300 Web Browsers

Claims

1. Computer, A receiving means for receiving an input of a first URL; performing a process of acquiring content associated with the first URL when the first URL does not match a second URL already input to the receiving means when the receiving means receives the input of the first URL; a control means for executing control not to perform an acquisition process of the content associated with the first URL when the first URL matches the second URL; A program characterized by causing the program to function as a

2. the control means executes control to perform an acquisition process of the content associated with the second URL; The program according to claim 1, characterized in that, when the first URL matches the second URL, the control means executes control not to read the cache of the content linked to the second URL.

3. 2. The program according to claim 1, wherein, when the first URL matches the second URL, the control means executes control not to access a server linked to the first URL.

4. update receiving means for receiving an instruction to update the content linked to the first URL; Functioning as a 2. The program according to claim 1, wherein, when the update receiving means receives the instruction, the control means executes control to perform an acquisition process of the content linked to the first URL.

5. 3. The program according to claim 2, wherein, when the content linked to the second URL is designated as being cache-prohibited, the control means executes control to perform an acquisition process of the content linked to the first URL.

6. a means for setting a timer for acquiring a time when the computer receives the input of the first and second URLs; Functioning as a The program described in claim 1, characterized in that when the time from when the input of the second URL is accepted to when the input of the first URL is accepted, as obtained by a timer set in the means, is equal to or greater than a first threshold value, the control means executes control to perform an acquisition process of content linked to the first URL.

7. 2. The program according to claim 1, wherein the accepting means accepts input of the first URL in response to the first URL being entered into a URL box and an operation item for confirming the input being pressed.

8. 2. The program according to claim 1, wherein the program is installed in an image forming apparatus.

9. A receiving means for receiving an input of a first URL; performing a process of acquiring content associated with the first URL when the first URL does not match a second URL already input to the receiving means when the receiving means receives the input of the first URL; a control means for executing control not to perform an acquisition process of the content associated with the first URL when the first URL matches the second URL; An information processing device comprising:

10. a receiving step of receiving an input of a first URL; performing a process of acquiring content associated with the first URL when the first URL does not match a second URL that has already been input when the input of the first URL is received; a control step of executing control not to perform an acquisition process of the content linked to the first URL when the first URL matches the second URL; 13. A method for controlling an information processing apparatus comprising the steps of:

Images