Source: http://www.google.com/patents/US20040064469?ie=ISO-8859-1
Timestamp: 2015-01-26 23:19:57
Document Index: 278180031

Matched Legal Cases: ['art 101', 'art 103', 'art 105', 'art 101', 'art 101', 'art 103', 'art 105', 'art 101', 'art 101', 'art 101', 'art 101', 'art 103', 'art 103', 'art 2101', 'art 2103', 'art 2105', 'art 2101', 'art 2101', 'art 2103', 'art 2105', 'art 2101', 'art 2101', 'art 2206', 'art 2208', 'art 2206', 'art 2206', 'art 2206', 'art 2208', 'art 2208', 'art 2101', 'art 2101', 'art 2103', 'art 2103']

Patent US20040064469 - Information processing apparatus and information processing method - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsIn an information processing apparatus connectable to a terminal through a network, a terminal type of the terminal is specified based on a first request requesting Web information, said first request sent from the terminal through the network, and reference Web information is generated so as to include...http://www.google.com/patents/US20040064469?utm_source=gb-gplus-sharePatent US20040064469 - Information processing apparatus and information processing methodAdvanced Patent SearchPublication numberUS20040064469 A1Publication typeApplicationApplication numberUS 10/622,572Publication dateApr 1, 2004Filing dateJul 21, 2003Priority dateJul 22, 2002Also published asDE60324067D1, EP1385312A2, EP1385312A3, EP1385312A8, EP1385312B1, EP1936919A2, EP1936919A3, EP1936919B1, US7373347, US8005808, US20080189423Publication number10622572, 622572, US 2004/0064469 A1, US 2004/064469 A1, US 20040064469 A1, US 20040064469A1, US 2004064469 A1, US 2004064469A1, US-A1-20040064469, US-A1-2004064469, US2004/0064469A1, US2004/064469A1, US20040064469 A1, US20040064469A1, US2004064469 A1, US2004064469A1InventorsSeiji Takahashi, Hiroki Kobayashi, Sayaka KobayashiOriginal AssigneeSeiji Takahashi, Hiroki Kobayashi, Sayaka KobayashiExport CitationBiBTeX, EndNote, RefManReferenced by (8), Classifications (21), Legal Events (2) External Links: USPTO, USPTO Assignment, EspacenetInformation processing apparatus and information processing methodUS 20040064469 A1Abstract In an information processing apparatus connectable to a terminal through a network, a terminal type of the terminal is specified based on a first request requesting Web information, said first request sent from the terminal through the network, and reference Web information is generated so as to include reference path created by adding terminal type information showing the specified terminal type to a path indicated in the first request for accessing the Web information and to allow the terminal to automatically accesses to the reference path. Then, the reference Web information is sent to the terminal as a response with respect to the first request, and a second request for requesting the Web information specified by the reference path is received. Images(60) Claims(34)
[0101] An information processing apparatus according to a first embodiment of the present invention includes at least one of a plurality of different image forming functions such as a printer, a FAX, and a copier, and also provides information concerning the image forming functions by a plurality of Web applications. In the present invention, for the sake of convenience, a case in that information concerning a copying process and a plotter for conducting a copy will be mainly described. The information processing apparatus provides the information by a suitable size for a display screen of a terminal requesting the information. [0102]FIG. 1 is a block diagram showing a hardware configuration of the information processing apparatus according to the first embodiment of the present invention. In FIG. 1, the information processing apparatus 100 is controlled by a computer, and includes a CPU (Central Processing Unit) 11, a ROM (Read-Only Memory) 12, a RAM (Random Access Memory) 13, a non-volatile RAM 14, a real time clock 15, an Ethernet� I/F (Interface) 21, a USB (Universal Serial Bus) 22, an IEEE 1284 (Institute of Electrical and Electronics Engineers 1284) 23, a hard disk I/F 24, an engine I/F 25, and an RS-232C I/F 26, which are mutually connected through a system bus B. [0103] The CPU 11 controls the information processing apparatus 100 according to the programs stored in the ROM 12. For example, the RAM 13 includes an area to assign to each resource connected to one of the interfaces 21 through 26. The non-volatile RAM 14 stores information necessary for a process by the CPU 11 to control the information processing apparatus 100. The real time clock 15 clocks a present time, and also is used by the CPU 11 to synchronize the process. [0104] The Ethernet� I/F 21 is used to connect to an interface cable for the Ethernet� I/F 21 such a 10 BASE-T or 100 BASE-TX. The USB I/F 22 is used to connect to an interface cable based on the USB standard. The IEEE1284 23 is used to connect to an interface cable based on the IEEE1284 standard. [0105] The hard disk I/F 24 is used to connect to a hard disk 34. Document data concerning a document that is sent through a network to print or image data after a printing process is stored in the hard disk 34 through the hard disk I/F 24. The engine I/F 25 is used to connect to a plotter 35-1 for printing to a predetermined medium based on the document data and a scanner 35-2 for reading the image data. The RS-232C I/F 26 is used to connect to an operation panel 36 that displays information to a user or obtains information input or set by the user. [0106] Next, a functional configuration of the information processing apparatus 100, which includes the hardware configuration as shown in FIG. 1, conducts a plurality of different image forming processes, and includes a plurality of Web applications, will be described with reference to FIG. 1. [0107]FIG. 2 is a block diagram showing the functional configuration of the information processing apparatus according to the first embodiment of the present invention. In FIG. 2, the information processing apparatus 100 is capable of connecting to terminals 40 including a client PC 41, a mobile phone 42, and a PDA (Personal Digital Assistant) terminal 43, which have different utilization forms of a display screen. The information processing apparatus 100 is a computer to provide information as a response with respect to a request sent from each of the terminals 40. [0108] The information processing apparatus 100 mainly includes a network controlling part 101, a sequence control library 110, a Web application distribution common library 120, a Web page handler 200, a SOAP (Simple Object Access Protocol) library 201, an XML (extensible Markup Language) library 203, an XSLT (XSL Transformations) processor 205, a Web page function (WPF) 300, a printer controlling part 103, and a scanner controlling part 105. [0109] The network controlling part 101 includes at least an HTTP daemon 2 for conducting a communication control in accordance with an HTTP (Hyper Text Transfer Protocol). The network controlling part 101 receives the request from each terminal 40 and provides information as a response with respect to the request. [0110] In order to execute a predetermined process so as to succeed to attribute information showing attributes concerning a utilization form of a Web browser of the terminal 40 while a user conducts page transitions (browse one Web page linked from another Web page) among a plurality of Web applications 301, when the HTTP daemon 2 receives the request from the terminal 40, and additionally provides a temporary common path information, and a Web application ID and a CGI (Common Gateway Interface) which are referred to execute the predetermined process, to the URL indicated by the request. The HTTP daemon 2 adds necessary information and creates the URL as shown in FIG. 3. FIG. 3 is a diagram showing a URL configuration according to the first embodiment of the present invention. In FIG. 3, the URL is mainly formed by a common path information 60 a and a relative path information 60 b. [0111] When the HTTF daemon 2 receives a first page request from the terminal 40, for example, only �http://AAA� is indicated as the URL. The HTTP daemon 2 additionally provides predetermined �/TERMINAL/PROFILE/LANG/webDefaultApl/defaul.cgi� to the URL. [0112] For example, the URL formed as described above includes a protocol type 61 for specifying access means such as the http, an IP address 62 shown as �AAA�, a terminal type information 63 a shown as �TERMINAL�, a profile information 63 b shown as �PROFILE�, a language information 63 c shown as �LANG�, a Web application ID 64 shown as �webDefaultApl�, and page information 65 shown as �default.cgi�. [0113] The protocol type 61, the IP address 62, the terminal type information 63 a, the profile information 63 b, the language information 63 c are set as the common path information 60 a. After that, the common path information 60 a is succeeded every time at the page transition, and is referred by the plurality of Web applications 301 being chained by the page transition. And the relative path information 60 b is formed by the Web application ID 64 and the page information 65. [0114] Referring to FIG. 2 again, explanation of each processing part will be continued. [0115] The sequence control library 110 is a processing part that is shared with the plurality of Web applications 301 and handles by a predetermined sequence controlling process a difference between a process sequence of sending and receiving data through the Internet 16 and another process sequence of sending and receiving data to/from each of the Web applications 301. [0116] The Web application distribution common library 120 is a processing part that is shared with the plurality of Web applications 301, and that analyzes a request from the terminal 40 and generates a response for the terminal 40. The Web application distribution common library 120 converts the response described in XML by the Web page handler 200 into the response described in a display format by HTML (HyperText Markup Language) corresponding to the terminal type of each terminal 40 by using the XSLT processor 205. [0117] The Web page handler 200 is a processing part that converts a process language understandable for the Web applications 301 into another process language understandable in the communication control conducted with the terminal 40 for the request and the response. The Web page handler 200 calls one Web application 301 corresponding to the request via a CGI indicated by the request. Also, the Web page handler 200 sends a serialization request to the SOAP library 201 to serialize process result data provided from the Web page function 300. [0118] The SOAP library 201 converts the process result data given by variables of C language into a description in XML so as to serialize the process result. In the first embodiment, serialization means to describe the process result provided from the Web page function 300 in XML. [0119] The XML library 203 is used by the SOAP library 201 to serialize the process result by describing in XML. Also, the XML library 203 is used by the XSLT processor 205 to generate the process result described in HTML. [0120] The XSLT processor 205 converts the process result described in XML into HTML by using the XML library 203 based on a style sheet 430 described in XSL (eXtensible Stylesheet Language) corresponding to the Web application 301 indicated by the request from the terminal 40. The style sheet 430 is prepared beforehand by corresponding to each Web application 301 and instructs a conversion method for each size of the display screens. [0121] When the Web page function 300 is called from the Web page handler 200, for example, inquires the printer controlling part 103 or the scanner controlling part 105 mounted to the information processing apparatus 100 through an API (Application Program Interface) 17, obtains information showing a status of the plotter 35-1 or the scanner 35-2, and then provides the information to the Web page handler 200. Moreover, the Web page function 300 inquires the network controlling part 101 through the API 17, obtains information from the network controlling part 101, and provides the information to the Web page handler 200. [0122] Next, a detailed configuration for executing the Web applications will be described with reference to FIG. 4, FIG. 5A and FIG. 5B. FIG. 4 is a block diagram for explaining an execution of the Web applications according to the first embodiment of the present invention. FIG. 5A and FIG. 5B are diagrams showing hash lists according to the first embodiment of the present invention. In FIG. 4, for example, in order to provide information based on the configuration of the URL as shown in FIG. 3, the Web page handler 200 includes a default handler 210 executed at a first request from the terminal 40, a network setting handler 220 executed by a page transition in accordance with the instruction from the terminal 40, a system configuration information providing handler 230 similarly executed by page transition, and a like. [0123] Corresponding to the handlers in the Web page handler 200, respectively, the Web page function 300 includes the plurality of Web applications 301: a Web default application 310, a Web network setting application 320, a Web system configuration information providing application 330, and a like. [0124] Until an initial display screen is displayed at the terminal 40, the default handler 210 sequentially calls the Web default application 310 through �default.cgi�, �mainFrame.cgi�, �manuPage.cgi�, �topPage.cgi�, and �headerPage.cgi� indicated by the page information 65 in accordance with a format of the URL shown in FIG. 3. As a result, for example, a status of the device such the plotter 35-1 or scanner 35-2 mounted in the information processing apparatus 100 is displayed at the terminal 40. [0125] The network setting handler 220 calls a function for the Web network setting application 320 for setting up network setup information inputted by a user of the terminal 40 in the information processing apparatus 10. In addition, the system configuration information providing handler 230 calls the Web system configuration information providing application 330 so as to obtain a system configuration information of the information processing apparatus 100 in response to a request from the terminal 40. [0126] The Web application distribution common library 120 obtains the Web application ID 64 from a URL, and refers to a hash list 50 a shown in FIG. 5A. When the Web application ID 64 shows �webDefaultApl�, the Web application distribution common library 120 executes �default_handler� In the same manner, when the Web application ID 64 shows another Web application ID, the Web application distribution common library 120 refers to the hash list 50 a, and executes a handler corresponding to the Web application ID to be executed. [0127] In addition, each of the handlers 210, 220, and 230 in the Web page handler 200 obtains the page information 65 from the URL, refers to the hash list shown in FIG. 5B, and calls a function corresponding to the page information 65. For example, when the page information 65 shows �default.cgi�, �default( )� is obtained to call as a function. Similarly, when the page information 65 shows another CGI, each of the handlers 210, 220, and 230 refers to hash list 50 b and obtains a function to call. [0128] Moreover, in order to conduct the XSL conversion request which converts the process result described by XML to the XSLT processor 205 into HTML, the Web application distribution common library 120 obtains the page information 65 from the URL specified as a Web page function ID, and obtains a corresponding style sheet 430 by referring to the hash list 50 b shown in FIG. 5B. For example, when the page information 65 shows �topPage.cgi�, the Web application distribution common library 120 obtains �topPage.xsl� as a style sheet necessary for the XSL conversion from the hash list 50 b. Similarly, when the page information 65 is another CGI, the Web application distribution common library 120 obtains a style sheet necessary for the XSL conversion by referring to the hash list 50 b. [0129] In FIG. 4, FIG. 5A, and FIG. 5B, when the page information 65, as the Web page function ID, of the URL is �default.cgi�, the function default( ) is executed, and the terminal type of the terminal 40 is determined. Accordingly, the terminal type information of the URL which is temporarily created by the HTTP daemon 2 is replaced with the determined terminal type and the initial display screen where the URL showing the determined terminal type is set is created. [0130] When the page information 65 is �mainFrame.cgi�, a function mainFrame( ) is executed, and a predetermined CGI is set for each of frames forming the initial display screen. For example, the function mainFrame( ) generates information so as to configure a frame displaying a menu page, a frame displaying a top page, and a frame displaying a header page. [0131] When the page information 65 is �menuPage.cgi�, the function menuPage( ) is executed, and the information for creating a menu page is generated. When the page information 65 is �topPage.cgi�, a function �topPage.cgi� is executed. For example, the information is generated so as to create a top page displaying a status of a printer as a status of the plotter 35-1. When the page information 65 is �headerpage.cgi�, a function headerPage( ) is executed so as to generate information for creating the top page. [0132] Moreover, when the page information 65 is �netsetting.cgi�, a function netsetting( ) is executed so as to generate the information for creating a page for the system setting. When the page information 65 is �sysconfig.cgi�, a function sysconfig( ) is executed, information showing a system configuration is generated. [0133] For the sake of convenience, names of the Web application ID and the Web page handler are unified. But it is not limited to do so since the hash list 50 a corresponds the Web application ID to the Web page handler. Also, names of the Web page function ID, the function, the style sheet are unified in the same manner. But it is not limited to do so since the hash list 50 b corresponds the Web page function ID, the function, and the style sheet each other. [0134] Next, a process flow until information is provided with respect to the first request from the terminal 40 will be described FIG. 6 and FIG. 7 are diagrams showing the process flow for default.cgi according to the first embodiment of the present invention. [0135] In FIG. 6, the terminal 40 sends a request additionally providing user agent information by using a GET method of the HTTP (step S11). For example, the terminal 40 sends the request by indicating a URL �http://AAA�. [0136] When the information processing apparatus 100 receives this request, the HTTP daemon 2 of the information processing apparatus 100 additionally provides the terminal type information 63 a, the profile information 63 b, the language information 63 c, the Web application ID 64, the page information 65 to the URL �http://AAA�, and then sends this request to the sequence control library 110 (step S12) For example, the HTTP daemon 2 additionally provides �TERMINAL� as the terminal type information 63 a, �PROFILE� as the profile information 63 b, �LANG� as the language information 63 c, �webDefaultApl� as the Web application ID 64, and �default.cgi� as the page information 65, to the URL �http://AAA�, so as to form �http://AAA/TERMINAL/PROFILE/LANG/webDefaultApl/default.cgi�. [0137] The sequence control library 110 calls the Web application distribution common library 120 (step S13). When calling the Web application distribution common library 120, the sequence control library 110 sets the HTTP connection information showing information concerning a connection with the terminal 40, and the hash lists 50 a and 50 b as arguments. In the following, the hash lists 50 a and 50 b are generically called hash lists That is, the hash lists include the hash lists 50 a and 50 b and other hash lists. The HTTP connection information uniquely specifies the connection with the terminal 40 until the connection is disconnected. [0138] The Web application distribution common library 120 specifies and calls the default handler 210 (�default_handler�) from the hash list 50 a, as the Web page handler 200 corresponding to the Web application ID 64 showing �webDefaultApl� based on the URL generated by the HTTP daemon 2 (step S14). [0139] In the Web page handler 200, the default handler 210 obtains the page information 65 showing �default.cgi� from the URL, and specifies and calls the function default( ) from the hash list 50 b as the Web page function 300 corresponding to �default.cgi� (step S15). In this case, the HTTP connection information is set as the argument. For example, in a case in that the Web page function 300 is developed by C language, the Web page handler 200 converts into a process type of C language and then calls the function default( ). [0140] By executing the function default( ), based on the HTTP connection information, terminal information is analyzed and a URL calling the initial display screen is created by including the common path information 60 a determined by the function default( ) (step S16) A process result data including the URL is returned to the default handler 210 in the Web page handler 200 (step S17). In a process by default.cgi, the common path information 60 a is determined, and a URL is determined by the common path information 60 a and the relative path information 60 b for determining a frame configuration of the initial display screen For example, �/pc/admin/ja� is determined as the common path information 60 a and �/webDefaultApl/mainFrame.cgi� for dividing the initial display screen into a plurality of display areas by frames is determined as the relative path information 60 b. [0141] The default handler 210 sends a serialization request to the SOAP library 201 in order to describe the process result data in XML (Step S18) For example, the SOAP library 201 creates a DOM (Document Object Model) based on the process result data shown by a C language structure, additionally provides necessary elements and attributes (step S19), and describes the process result data in XML by the XML library 203 (step S20). The process result data described in XML is provided to the default handler 210 as the serialization result by the SOAP library 201 (step S21) In the Web page handler 200, the default handler 210 provides the serialization result as display data �Response DOM� to display at the terminal 40, to the Web application distribution common library 120 (step S22). [0142] In order to convert the display data described in XML into a description of HTML corresponding to the terminal type of the terminal 40, the Web application distribution common library 120 refers to the hash list 50 b, obtains the style sheet �default xsl� corresponding to the page information 65 showing �default.cgi�, and sends the XSL conversion request to the XSLT processor 205 (step S23). The display data �Response DOM� and the style sheet �default.xsl� are set as arguments for the XSL conversion request. [0143] When the XSLT processor 205 receives the XSL conversion request, the XSLT processor 205 executes the style sheet �default.xsl� indicated by the argument. Accordingly, the XSLT processor 205 analyzes syntax of the display data �Response DOM� described in XML (parse XML, creates a DOM, additionally provides elements and attributes (step S24), and converts into the description of HTML by using the XML library 203 (step S25). The XSLT processor 205 provides the description of HTML to the Web application distribution common library 120 as a XSL conversion result (step $26). [0144] The process result described in HTML by the Web page function 300 when the page information 65 shows �default.cgi� is output as a default HTML to the Web application distribution common library 120. In the default HTML, �mainFrame.cgi� is described in HTML to be called. The default HTML is output as a default HTML response. [0145] The default HTML response is sequentially provided from the Web application distribution common library 120 to the sequence control library 110 (step S27) and is provided from the sequence control library 110 to the HTTP daemon 2 (step S28) After that, the default HTML response is sent as a response with respect to the request of the terminal 40 in step S11 by the HTTP daemon 2 (step S29). Then, the process flow for executing the Web default application 310 by the default.cgi is terminated. [0146] In step S17, the common path information 60 a is determined and simply the common path information 60 a is added to the relative path information 60 b. Accordingly, the Web default application 310 may describe the process result in HTML and output the process result described in HTML. Thus, steps S18 through S26 may be omitted. [0147] Next, an analyzing process for the terminal information executed by the function default( ) in step S16 shown in FIG. 6 will be described with reference to FIG. 8 through FIG. 11 in detail. FIG. 8 is a flowchart diagram for explaining the analyzing process for the terminal information according to the first embodiment of the present invention. FIG. 9 is a diagram showing a data structure of the HTTP connection information according to the first embodiment of the present invention. FIG. 10 is a diagram showing a data structure of the HTTP request information according to the first embodiment of the present invention. FIG. 11 is a diagram showing a header information list according to the first embodiment of the present invention. The data structures shown in FIG. 9 through FIG. 11 are referred by the analyzing process for the terminal information shown in FIG. 8. [0148] Prior to explanation of the analyzing process in FIG. 8, each of the data structures shown in FIG. 9 through FIG. 11 will be described. In FIG. 9, the HTTP connection information 340 is information generated for each connection. In the HTTP connection information 340, a script 346 describing �HTTP_REQUEST_INFO*request� indicates a pointer to a content of the request from the terminal 40 and a script 347 describing �HTTP_RESPONSE_INFO*response� indicates a pointer to a content of the response for the terminal 40. The HTTP request information is stored in a area indicated by the pointer shown by the script 346, as shown in FIG. 10. [0149] In FIG. 9, reference numerals 1340,1346, and 1347 will be referred in a second embodiment of the present invention. [0150] In FIG. 10, the HTTP request information 350 includes a remote address 351 showing an address of the terminal 40 which sent the request, a local address 352 showing an host address at a side where the request is received, a request method 353 such as POST, GET, or a like, a request URL 354 showing an URL of the request, an HTTP version 355 of the request, a header information list 360, and a encoded information list 357. [0151] In the request URL 354, the URL formed by the common path information 60 a and the relative path information 60 b as shown in FIG. 3 is set by the sequence control library 110. The HTTP request information 350 is provided to the Web page handler 200 and to the Web page function 300 at the same time of the HTTP connection information 340. Accordingly, the Web page handler 200 and the Web applications 301 share and refer to the common path information 60 a. [0152] In FIG. 10, reference numerals 1350, 1351, 1352, 1353, 1354, 1355, 1360, and 1357 will be referred in the second embodiment of the present invention. [0153] And for example, the header information list 360 is structured as shown in FIG. 11. As shown in FIG. 11, the header information list 360 includes user agent information 365 showing �User-Agent:Mozilla/4.0(compatible;MSIE 6.0;Windows NT 5.0;Q312461;NET CLR 1.0.3705)�. The user agent information 365 includes the terminal type of the terminal 40. Thus, this script of the user agent information 365 is analyzed, so as to provide information corresponding to the size of the display screen of the terminal 40. [0154] In FIG. 8, in response to a call of the function( ), the Web default application 310 obtains the HTTP request information 350 from the HTTP connection information 340 (step S1). Moreover, the Web default application 310 obtains the user agent information 365 from the HTTP request information 350 (step S2). Then, based on a Web browser type of the user agent information 365, the Web default application 310 refers to a Web browser type�terminal type correspondence table (FIG. 12) and specifies the terminal type of the terminal 40 (step S3). [0155] The Web default application 310 determines whether or not the terminal type is determined based on the Web browser type (step S4). When the terminal type is determined, the Web default application 310 goes to step S38. When the terminal type is not determined, the Web default application 310 refers to a Web browser OS�terminal type correspondence table based on the Web browser OS of the user agent information 365 and specifies the terminal type of the terminal 40 (step S5). [0156] The Web default application 310 determines whether or not the terminal type is determined based on the Web browser OS (step S6). When the terminal type is not determined, the default application 310 outputs error information showing that the terminal type is not supported (step S7), and then the analyzing process for the terminal information is terminated. In step S7, the Web default application 310 sets a predetermined device type as the terminal type of the terminal 40, instead of outputting the error information showing that the terminal type is not supported, and then the Web default application 310 goes to step S8. [0157] On the other hand, in steps 54 and S6, when the terminal type is determined, the Web default application 310 sets the terminal type to the terminal type information 63 a of the URL (step S8), and then terminates the analyzing process for the terminal information. [0158]FIG. 12 is a diagram showing the Web browser type�terminal type correspondence table according to the first embodiment of the present invention. In FIG. 12, the Web browser type�terminal type correspondence table 370 includes items of the Web browser type, the terminal type, and the like. The terminal type corresponding the Web browser type is managed in the Web browser type�terminal type correspondence table 370. [0159] For example, as the Web browser type, �DOCOMO��, �xiino��, �MSPIE��, �HandHTTP��, �MSIE��, �Mozilla��, �mozilla/5��, and �Netscape6�� are managed in the Web browser type�terminal type correspondence table 370. [0160] The terminal types are �IMODE��, �PDA�, �0�, �PC�, and a like. The terminal type corresponding to the Web browser type �DOCOMO�� is �IMODE��. The terminal type corresponding to the Web browser type �xiino��, and �MSPIE��, �HandHTTP�� is �PDA�. The terminal type corresponding to the Web browser type �Mozilla��, �mozilla/5��, and �Netscape6�� is �PC�. The terminal types are not limited to the above-described terminal types but various terminal types can be managed. [0161] The terminal type �0� denotes that the terminal type cannot be specified. In a determination process in step S4 of FIG. 8, the terminal type is not determined For example, in a case of a request from InternetExploer�, generally, the Web browser type �MSPIE�� is set to the user agent information 365 when the terminal type is �PDA�, and the Web browser type �MSIE�� is set to the user agent information 365 when the terminal type is �PC�. However, even if the terminal type is �PDA�, there is a case in that the Web browser �MSIE�� is set to the user agent information 365. Accordingly, since the terminal type corresponding to the Web browser type �MSIE�� cannot be specified beforehand, �0� is set to the terminal type for the Web browser type �MSIE��. [0162] In a case in that the terminal type cannot be specified as described above, a correspondence table shown in FIG. 13 is referred to. FIG. 13 is a diagram showing the Web browser OS�terminal type correspondence table according to the first embodiment of the present invention In FIG. 13, the Web browser OS�terminal type correspondence table 380 includes items of the Web browser OS, the terminal type, and the like The Web browser OS corresponding to the terminal type is managed. [0163] For example, as the Web browser OS, there are �Windows 3.1��, �Windows 95��, �Windows 98��, �Windows ME��, �Windows NT��, �Windows 2000��, �Windows XP��, �Mac 68K��, �Mac Power PC��, �Solaris��, �Linux��, �Free BSD��, �AIX��, �IRIX��, �HP��, �OS/2��, �Windows CE��, and a like. [0164] There are �PDA�, �PC�, and a like as the terminal types. The mobile phone 42 is included in the terminal type �PDA�. In the Web browser OS�terminal type correspondence table 380 shown in FIG. 13, the terminal type corresponding to the Web browser OS from �Windows 3.1�� to �OS/2�� is �PC�. And the terminal type corresponding to the Web browser OS �Windows CE��, is �PDA�. [0165] The terminal type can be specified by referring to the Web browser type�terminal type correspondence table 370 and the Web browser OS�terminal type correspondence table 380. [0166] The default HTML output by default.cgi will be described with reference to FIG. 14. FIG. 14 is a diagram showing an example of the default HTML output according to the first embodiment of the present invention. In FIG. 14, the default RTML 400 is not displayed at the terminal 40, but a script 401 that is Javascript� calls the top page. [0167] By a script 402 showing �self.document.cookie=�cookieOnOffchecker=on; path=/��, information concerning the Web browser of the terminal 40 is obtained. By a scrip 403 showing �self.location.pathname=�/pc/admin/ja/webDefaultApl/main frame.cgi��, the terminal type �pc� is succeeded, and the Web default application 310 of the Web page function 300 is executed. That is, a mainframe HTML is requested by �mainframe.cgi�. During a series of page transitions conducted by a user after that, an absolute path is indicated by a script 403 to be a reference for a relative path indicated by <a href> tag. [0168] In a case in which information is provided to the client pc 41 through the Internet 16, the display screed is often divided into a plurality of display areas by frames. The default output is illustrated in such a case in FIG. 14. On the other hand, in a case in that the initial display screen is displayed without dividing into the plurality of display areas, for example, the script 403 describes �self location.pathname=�/pc/admin/ja/webDefaultApl/topPage.cgi��. The top page is directly called to provide and display information. [0169] In the following, a process will be described in that information is provided corresponding to the terminal type of the terminal 40 in a case of dividing the display screen into the plurality of display areas by frames. [0170] After that, when the page transition is conducted, only the relative path information 60 b is indicated but the terminal type �PC� included in the common path information 60 a is always succeeded. That is, the same common path information 60 a is shared and referred by the plurality of the Web applications 301. [0171]FIG. 15 and FIG. 16 are diagrams showing a process flow by mainFrame.cgi according to the first embodiment of the present invention. In FIG. 15, the terminal 40 requests a mainframe HTML (mainfram HTML request) (step S31) �/pc/admin/ja/webDefaultApl/mainFrame.cgi� is indicated, and the mainfram HTML request is conducted by a GET method attaching with form data. The HTTP daemon 2 of the information apparatus 100 sends the HTTP connection information 340 and the hash lists to the sequence control library 110 (step S32). [0172] In this case, by the HTTP daemon 2, �GET� is set to the request method of the HTTP request information 350 related to the HTTP connection information 340, and �/pc/admin/ja/webDefaultApl/mainFrame.cgi� is set to the request URL 354. By this indication, when a next request is received from the terminal 40 by the relative path after that, the common path information 60 a showing �/pc/admin/ja� can be referred Accordingly, it is easily determined that the terminal type of the terminal 40 is �PC.� Also, the form data received from the terminal 40 is set to the hash lists by the HTTP daemon 2. [0173] The sequence control library 110 calls the Web application distribution common library 120 (step S33) In this case, the sequence control library 110 sets the HTTP connection information showing information concerning the connection with the terminal 40 and the hash lists as arguments. [0174] The Web application distribution common library 120 specifies and calls the default handler 210 (�default_handler�) from the hash list 50 a as the Web page handler 200 corresponding to the Web application ID 64 indicating �webDefaultApl� based on the URL (step S34). [0175] In the Web page handler 200, the default handler 210 obtains the page information indicating �mainFrame.cgi� from the URL, and specifies and calls the function mainFrame( ) from the hash list 50 b as the Web page function 300 corresponding to �mainFrame.cgi� (step S35). In this case, the HTTP connection information is set as an argument. For example, in a case in that the Web page function 300 is developed by C language, the Web page handler 200 converts into a process type of C language and calls the function mainFrame( ). [0176] By executing the function mainFrame( ), frame information to form the initial display screen (topPage.cgi) is created (step S36). The frame information is sent to the default handler 210 in the Web page handler 200 as the process result data (step S37). [0177] In the following, the serialization process for describing in XML in steps S38, S39, S40, S41, and S42 is the same as the serialization process in steps S18, S19, S20, S21, and 522 and explanation thereof will be omitted. [0178] In order to convert the display data described in XML into a description in HTML corresponding the terminal type of the terminal 40, the Web application distribution common library 120 refers to the hash list 50 b, obtains the style sheet �mainFrame.xsl� corresponding to the page information 56 indicating �mainFrame cgi�, and conducts the XSL conversion request with respect to the XSLT processor 205 (step S43). In this case, the display date �Response DOM� and the style sheet �mainFrame.xsl� are set as the arguments When the XSLT processor 205 receives the XSL conversion request, the XSLT processor 205 executes the style sheet �mainFrame.xsl� indicated by the argument. Accordingly, the XSLT processor 205 selects one template corresponding to the terminal type from descriptions of the style sheet, analyzes a syntax of the display data �Response DOM� described in XML (parse XML), creates a DOM, additionally provides elements and attributes (step S44), and converts into the description of HTML by using the XML library 203 (step S45). When the terminal type information 63 a shows �PC�, HTML data for dividing the display screen into the plurality of display areas by frames is output. On the other hand, when the terminal type information 63 a shows �PDA�, HTML data described by JavaScript� for directly calling the top page is output. [0179] The XSLT processor 205 provides the description in HTML as the XSL conversion result to the Web application distribution common library 120 (step S46). The process result described in HTML by the Web page function 300 in a case in that the page information 65 shows �mainFrame.cgi� is output to the Web application distribution common library 120 as the mainframe HTML. The mainfram HTML is described in HTML so that �manuPage.cgi� is called from a frame forming the menu page, �topPage.cgi� is called from a frame forming the top page, and �headerPage cgi� is called from a frame forming the header page. [0180] This mainframe HTML response is sequentially provided from the Web application distribution common library 120 to the sequence control library 110 (step S47) and from the sequence control library 110 to the HTTP daemon 2 (step S48) Accordingly, the mainframe HTML response is sent to the terminal 40 in response to the request of the terminal 40 in step S31 in accordance with HTTP by the HTTP daemon 2 (step S49). Then, the process flow executed by the mainFrame.cgi is terminated. [0181] A mainframe HTML output by mainFrame.cgi in a case in that the terminal 40 is the client PC 41 will be described with reference to FIG. 17 FIG. 17 is a diagram showing an example of the mainframe HTML output for the PC according to the first embodiment of the present invention. In FIG. 17, the mainframe HTML 410 creatges three frames on the Web browser of the terminal 40 by a script 411, and a page from each <frame> tag is called through a CGI. [0182] A script 412 showing <frame noresize src=�/webDefaultApl/headerPage.cgi� name=�header� marginheight=�0� marginwidth=�0� scrolling=�no�> displays the header page in a frame. By a script 413 showing �/webDefaultApl/headerPage.cgi�, the default handler 210 is executed based on �webDefaultApl�, the function headerPage( ) of the Web default application 310 is executed based on �headerPage.cgi�, and then the header page is displayed in the frame. [0183] Also, a script 414 showing <frame src=�/webDefaultApl/menuPage.cgi� name=�menu�marginheight=�0� marginwidth=�0� scrolling=�auto�>displays the menu page in a frame. By a script 415 showing �/webDefaultApl/menuPage.cgi�, the default handler 210 is executed based on �webDefaultApl�, the function menuPage( ) of the Web default application 310 is executed based on �menuPage.cgi�; and the menu page is displayed in the frame. [0184] Furthermore, a script 416 showing <frame src=�/webDefaultApl/topPage.cgi� name=�top� marginheight=�0� marginwidth=�0� scrolling=�auto�>displays the top page in a frame. By the script 417 showing �/webDefaultApl/topPage.cgi�, the default handler 210 is executed based on �webDefaultApl�, the function topPage( ) of the Web default application 310 is executed based on �topPage.cgi�, and the top page is displayed in the frame. Since the scripts 412, 414, and 416 indicates only relative path information 60 b, the common path information 60 a is indicated by the URL. [0185] In FIG. 17, when the terminal 40 is the mobile phone 42 or the PDA terminal 43, the mainframe HTML may be created so as to call only topPage.cgi without structuring frames For example, in the mainframe HTML, similar to the description of the default HTML output shown in FIG. 14, jumpToTopPage( ) may be described so as to directly call topPage.cgi by �self.location.pathname=�/pda/admin/ja/webDefaultApl/top Page.cgi��, instead of describing jumpToMainFrame( ). [0186]FIG. 18 and FIG. 19 are diagrams showing a process flow by topPage.cgi according to the first embodiment of the present invention In FIG. 18, the terminal 40 requests an HTML for displaying a status of the plotter 35-1 or the scanner 350-2 mounted to the information processing apparatus 100 (top page HTML request) (step S51). The top page HTML request is conducted by the GET method in which �topPage.cgi� is indicated and the form data is attached. [0187] The HTTP daemon 2 of the information processing apparatus 100 sends the HTTP connection information 340 and the hash lists to the sequence control library 110 (step S52) In this case, the HTTP daemon 2 sets �GET� to the request method of the HTTP request information 350 related to the HTTP connection information 340, and indicates �topPage.cgi� to the URL of the request. In addition, the HTTP daemon 2 sets the form data received from the terminal 40 to the hash lists. [0188] The sequence control library 110 calls the Web application distribution common library 120 (step S53) In this case, the sequence control library 110 sets the HTTP connection information and the hash lists as arguments. [0189] The Web application distribution common library 120 specifies and calls the default handler 210 (�default_handler�) from the hash list 50 a as the Web page handler 200 corresponding to the Web application ID 64 showing �webDefaultApl� based on the URL (step S54). [0190] In the Web page handler 200, the default handler 210 obtains the page information 65 showing �topPage.cgi�, and specifies and calls the function topPage( ) from the hash list 50 b as the Web page function 300 corresponding to �topPage.cgi� (step S55). In this case, the HTTP connection information 340 is set as an argument. [0191] For example, in a case in that the Web page function 300 is developed by C language, the Web page handler 200 converts into a process type of C language and calls the function topPage( ). [0192] By executing the function topPage( ), the Web default application 310 requests information including a device name, a comment, and a like to the network controlling part 101 through the API 17, in order to display the status of a device (for example, plotter 35-1 as the printer) at the initial display screen (topPage.cgi) (step S56-2). The network controlling part 101 provides the information including the device name, the comment, and the like in response to the request (step S56-4). [0193] For example, the Web default application 310 of the Web page function 300 requests the status of the printer to the printer controlling part 103 through the API 17 (printer status request) (step S56-6). The printer controlling part 103 provides the status of the plotter 35-1 as a printer status to the Web default application 310 (step S56-8). [0194] Then, the Web default application 310 provides the printer status, and the terminal type information 63 a, the profile information 63 b and the language information 63 c from the request URL 354 of the HTTP request information 350 as the process result data to the default handler 210 in the Web page handler 200 (step S57). [0195] In the following, the serialization process for describing in XML in steps s58, S59, S60, S61, and S62 is the same as the serialization process in steps S18, S19, S20, S21, and S22, and explanation thereof will be omitted. [0196] In order to convert the display data described in XML into a description of HTML corresponding to the terminal type of the terminal 40, the Web application distribution common library 120 refers to the hash list 50 b, obtains the style sheet �topPage.xsl� corresponding to the page information 56 showing �topPage.cgi�, and conducts the XSL conversion request with respect to the XSLT processor 205 (step S63). In this case, the display data �Response DOM� and the style sheet �topPage.sl� are set as arguments. When the XSLT processor 205 receives the XSL conversion request, the XSLT processor 205 executes the style sheet �topPage.xsl� indicated in the argument. Accordingly, the XSLT processor 205 selects one template corresponding to the terminal type from descriptions of the style sheet, analyzes a syntax of the display data �Response DOM� described in XML (parse XML), creates a DOM, additionally provides elements and attributes (step S64), and converts into the description of HTML by using the XML library 203 (step S65). [0197] XSLT processor 205 provides the description of HTML as the XSL conversion result to the Web application distribution common library 120 (step S66). [0198] The process result described in HTML by the Web page function 300 in a case in that the page information 65 is �topPage.cgi� is output to the Web application distribution common library 120 as a top page HTML. Information concerning the status of the plotter 35-1 is described in the top page HTML. [0199] This top page HTML response is provided from the Web application distribution common library 120 to the sequence control library 110 (step S67), and then is provided from the sequence control library 110 to the HTTP daemon 2 (step S68). Subsequently, the HTTP daemon 2 sends the top page HTML response as a response in accordance with HTTP with respect to the request sent from the terminal 40 in step S51 (step S69) Then, the process flow executed by topPage.cgi is terminated. [0200] When the terminal 40 is the client PC 41, processes by headerPage.cgi and manuPage.cgi called from frames are executed in the same manner described above. Accordingly, the display screen divided by frames is displayed at the Web browser of the client PC 41. On the other hand, when the terminal 40 is the mobile phone 42 or the PDA terminal 43, since the display screen is not divided by the frames, only the top page is displayed at the display screen. [0201] The process result described in XML will be described. FIG. 20 is a diagram showing an example of the process result described in XML by topPage.cgi according to the first embodiment of the present invention. [0202] In an XML 420 shown in FIG. 20, the process result by the function topPage( ) of the Web default application 310 is shown by a script 421 showing from <networkResponse>to </networkResponse>. A script 422 showing <terminal>pc</terminal> shows that the terminal 40 is the client PC 41, a script 423 showing <language>ja</language> shows that a language of the Web browser of the terminal 40 is Japanese, and a script 424 showing <profile>admin</profile> shows that the user of the terminal 40 is an administrator. The scripts 422 through 424 show information based on the terminal type information 63 a, the profile information 63 b, and the language information 63 c of the common path information 60 a of the URL. [0203] A script 425 showing <deviceName>Printer 1</deviceName> shows that the device name is �Printer 1�. A script 426 showing <comment>XXXXXXXXX</comment> shows that the comment concerning �Printer 1� are �XXXXXXXXX�. A script 427 showing <status>Ready</status> shows that the status of �Printer 1� is �Ready�. [0204] In the first embodiment, the Web page handler 200 includes a function for serializing the process result data provided from the Web page function 300 by describing in XML. Accordingly, each of Web applications 301 of the Web page function 300 is not required to include a processing part for each terminal type. [0205] The style sheet 430, which converts the process result data described in XML to be serialized, into HTML by the XSLT processor 205 based on the terminal type, will be described with reference to FIG. 21. FIG. 21 is a diagram showing a description example of the style sheet for converting the process result from XML to HTML according to the first embodiment of the present invention. [0206] In the style sheet 430 shown in FIG. 21, it is determined by a script 431 whether or not an element sandwiched with <terminal>tags shown by a script 422 of the XML 420 of FIG. 20 includes a character string �pda�, that is, it is determined whether or not the XML 420 is the process result for the PDA terminal. A style sheet template for the PDA terminal is applied by a script 432 when the character string �pda� is included. Another style sheet template for the general PC is applied when the character string �pda� is not included. The style sheet template for the PDA terminal is described in a script 434, and the style sheet template for the general PC is described in a script 435. Details of each style sheet template are not shown in FIG. 21. [0207] For example, in a case in that a smaller size of the display screen of the mobile phone 42 or the PDA terminal 43 is concerned, the script 434 may describes the style sheet template for the PDA terminal so that images to display at the client PC 41 are not be displayed, a font size is indicated to be smaller than the PC, or the number of letters is indicated to be less than the PC. [0208] According to the first embodiment, the Web application distribution common library 120 includes a function for converting XML into HTML by XSL Therefore, it is possible to centralize to create an HTML response corresponding to the terminal type. Therefore, each of Web applications 301 in the Web page function 300 is not required to include processing parts corresponding to various terminal types, respectively. [0209] As described above, XSL for converting XML into HTML is prepared for each of Web applications 301 beforehand HTML showing the process result corresponding each of Web applications 301 is provided to the terminal 40, and then the process result is displayed at the Web browser of the terminal 40. [0210] When the terminal 40 is the client PC 41, for example, the process result of the function topPage( ) of the Web default application 310 is described in HTML as shown in FIG. 22. FIG. 22 is a diagram showing a description example of HTML for the PC in that the process result of the topPage.cgi is shown, according to the first embodiment of the present invention. In FIG. 22, HTML 440 for the PC is provided to the terminal 40 when the terminal 40 is the client PC 41, and the process result of the function topPage( ) of the Web default application 310 is displayed at the Web browser of the client PC 41 by a script 441. [0211] A script 442 showing <font size=�4�>System Status</font> shows to display �System Status� by a font size 4. A script 443 showing <img src=�printer.gif�> shows to display an image. A script 445 showing <p>System Name:Printer 1</p> shows to display �SystemName:Printer 1�, a script 446 showing <p>Comment:XXXXXXXXX</p> shows to display �Comment:XXXXXXXXX�, and a script 447 showing <p>System Status:Ready</p> shows to display �System Status:Ready�. [0212] In accordance with HTML 440 for the PC, the display screen as shown in FIG. 23 is displayed at the Web browser of the client PC 41. FIG. 23 is a diagram showing a display example of the system status at the client PC according to the first embodiment of the present invention. In FIG. 23, a display screen 450 is formed by three frames by mainFrame.cgi. The header page is displayed by headerPage.cgi, the menu page is displayed by menuPage.cgi, and the top page is displayed by topPage.cgi in three frames, respectively. [0213] In the top page, a text 452 showing �System Status� is displayed by the script 442 of HTML 240 of FIG. 22, an image 454 is displayed by the script 444 of FIG. 22, a text 455 showing �System Name:Printer 1� is displayed by the script 445 of FIG. 22, a text 456 showing �Comment:XXXXXXXXX� is displayed by the script 446 of FIG. 22, and a text 457 showing �System Status: Ready� is displayed by the script 447 of FIG. 22. [0214] In addition, for example, information as a header is displayed in the frame for displaying the header page. For example, texts 459 showing selectable menu items including �System Status�, �Network Settings�, �Device Configuration Information�, and a like are displayed in the frame for displaying the menu page. [0215] For example, �Network Settings� is described in HTML as<p><a href=�. . . /webNetsettingApl/netsetting.cgi� target=�top�>Network Settings</a></p>. Since only the relative path information 60 b is set in this URL, the common path information 60 a is succeeded as it is and information concerning �Network Settings� is displayed in the top page for the PC. That is, a path description from �webNetsettingApl� showing Web application ID is set as the relative path, and a current terminal type information 53 a is succeeded by a description �. . . /�. Also, the information concerning �Network Settings� is displayed in the top page for the PC by a description �target=�top��. [0216] Similarly, �Device Configuration Information� is described in HTML as �<p><a href=�. . . /webSysconfigApl/sysconfig.cgi� target=�top�>Device Configuration Information</a></p>�. Accordingly, since only the relative path information 60 b is set in this URL, the common path information 60 a is succeeded as it is and information concerning �Device Configuration Information� is displayed for the PC. [0217] In a case in that the client PC 41 sends a request to the information processing apparatus 100 according to the present invention, display screen 450 is shown at the client PC 41 However, in a case in that the mobile phone 42 or the PDA terminal 43 sends the same request to the information processing apparatus 100, HTML for the PDA terminal as shown in FIG. 24 is created and the display screen as shown in FIG. 25 is displayed at the PDA terminal 43, FIG. 24 is a diagram showing a description example of HTML for the PDA terminal where the process result of topPage.cgi is shown, according to the first embodiment of the present invention. In FIG. 24, HTML 440 a for the PDA terminal is provided to the terminal 40 when the terminal 40 is the PDA terminal 43, and then the process result of the function topPage( ) of the Web default application 310 is displayed at the Web browser of the PDA terminal 43 by a script 441 a. A script 442 a showing <font size=�3�>System status</font> shows to display �System Status� by a font size 3. The character font or a script 442 a is set smaller for the PDA terminal. [0218] The HTML 440 a for the PDA terminal does not include a script corresponding to the script 443 of HTML 440 of the client PC 41. [0219] Similar to the scripts 445 and 446 of HTML 440 for the PC, a script 445 a showing <p>System Name:Printer 1</p> shows to display �System Name:Printer 1�, and a script 446 a showing <p>Comment:XXXXXXXXX</p> shows to display �Comment:XXXXXXXXX�. [0220] For the PDA terminal 43 which display area is relatively smaller than the client PC 41, for example, a script 447 a corresponding to the script 447 of HTML 440 for the PC displays �Status:Ready�, instead of �System Status:Ready�, so that the number of letters to display is less than the PC. [0221] It is not preferred to divide the display screen into the plurality of display areas for the PDA terminal 43 Therefore, information displayed at other frames at the client PC 41 should be displayed within a single display screen (one page) at the PDA terminal 43. A script 448 a is a script described in HTML for displaying the menu page at the PC, and is described in HTML 440 a for the PDA terminal as �<p><a href=�. . . /webNetsettingApl/netsetting.cgi�>Network Settings</a></p>� and �<p><a href=�. . . /webSysconfigApl/sysconfig.cgi�>Device Configuration Information</a></p>�. Therefore, �Network Settings� and �Device Configuration Information� of selectable items displayed in the menu page of the client PC is displayed at the PDA terminal 43. �target=�top� is described in HTML 440 for the PC to indicate the frame to display. However, �target=�top� is omitted in the script 448 a. [0222] A display screen as shown in FIG. 25 is displayed at the Web browser of the PDA terminal 43 by HTML 440 a for the PDA terminal. FIG. 25 is a diagram showing a display example of the system status at the PDA terminal according to the first embodiment of the present invention. In FIG. 25, a display screen 450 a is formed by a single display screen which is not divided into the plurality of display areas by frames. [0223] A text 452 a showing �System Status� is displayed at the display screen 450 a by the script 442 a of HTML 240 a shown in FIG. 24. The image displayed at the client PC 41 is not displayed at the PDA terminal 43 and a text 455 showing �System Name:Printer 1�, is displayed by the script 445 a. A text 456 a showing �Comment:XXXXXXXXX� is displayed by the script 446 a. A text 457 a showing �Status:Ready�, which number of letters is less than that displayed at the client PC 41, is displayed by the script 447 a. [0224] Moreover, �Network Settings� and �Device Configuration Information�, which are selectable and displayed in the menu page at the client PC 41 are displayed as a text 458 showing selectable �Network Settings� and �Device Configuration Information� by the script 448 a In a state in that the display screen 450 a is displayed at the mobile phone 42 or the PDA terminal 43, when a user of the PDA terminal 43 selects �Network Settings�, the display screen as shown in FIG. 26 is displayed at the mobile phone 42 or the PDA terminal 43 since the URL is changed so that the common path information 60 a is succeeded and only the relative path information 60 b is shown FIG. 26 is a diagram showing a display example of �Network Settings� at the PDA terminal according to the first embodiment of the present invention. [0225] In FIG. 26, a display screen 460 a is displayed by a page transition from the display screen 450 a, and displays a page of �Network Settings� corresponding to the size of the display screen of the mobile phone 42 or the PDA terminal 43 since the common path information 60 a at the page transition. The user of the mobile phone 42 or the PDA terminal 43 is not required to conduct a setting to properly display �Network Settings� for the size of the display screen. [0226] If the user conduct the page transition (link from one page to another page) with respect to a conventional information processing apparatus that cannot specify the terminal type of the terminal 40, information for the display screen of the client PC 41 is displayed at the mobile phone 42 or the PDA terminal 43. As a result, the information is provided unsuitably as shown in FIG. 27. Since the terminal type information 53 a is not succeeded, letters being too large to read the whole sentence is displayed at the mobile phone 42 or the PDA terminal 43. Therefore, the conventional information processing apparatus cannot provide information suitable for the display screen. [0227] According to the first embodiment of the present invention, sine the HTTP daemon 2 forms the URL so as to call default.cgi when the HTTP daemon 2 receives the first request from the terminal 40, the information processing apparatus 100 can automatically set the URL including the common path information 60 a by default.cgi. Therefore, the user of the terminal 40 is not required to input information concerning the display screen of the terminal 40. [0228] The common path information 60 a is provided prior to the relative path information 60 b in the URL. Thus, a link from one page to another page can be indicated by only the relative path information 60 b. [0229] Moreover, the information processing apparatus 100 converts the description in XML into the description in HTML based on the terminal type information 53 a of the common path information 60 a by using a predetermined style sheet. Accordingly, in the information processing apparatus 100, a developer is not required to develop each of the Web applications 301 for each of the terminal types Therefore, it is possible to reduce workload of the developer. That is, it is possible for the Web applications 301 to output the process result in a unified manner. For example, a development of each of the Web applications 301 is not affected by a different size of the display screen, division of the display screen by the frames, and a like. [0230] According to the first embodiment of the present invention, as the terminal type, the client PC 41 is categorized into �PC�, and the mobile phone 42 and the PDA terminal 43 are categorized into �PDA�. However, in order to categorize the display screen in detail, various terminal types in addition to �PC� and �PDA� can be applied. Also, various categories can be applied to not only the size of the display screen but also to various characteristics of the display screen. [0231] Also, the present invention can be applied to a case in that the information processing apparatus 100 is connected to a large screen as another terminal 40. That is, as for the large screen, it is possible to change letters to be relatively bigger, to change the number of letters to be more, and a like in order to provide information by an effective display screen. Moreover, it is possible to provide a larger image or a plurality of images for the large screen, so as to effectively provide information In order to provide information corresponding to the terminal 40, in the information processing apparatus 100, the template corresponding to the terminal type in each style sheet 430 adjusts a display format of the process result provided from the Web page function 300 and additionally provides images to the process result. [0232] As described above, according to the present invention, since the terminal type information 63 a is set in the common path information 60 a when the request from the terminal 40 is received, even if the page transition is conducted among the plurality of the Web applications 301, the information corresponding to the same terminal type can be always provided at the Web browser of the terminal 40. [0233] Also, a processing part for describing the process result in XML and a processing part for converting XML into HTML are provided separately from the plurality of Web applications 301 in the Web page function 300. [0234] [Second Embodiment]
[0325] An information processing apparatus 2100 will be described according to a third embodiment of the present invention In the third embodiment according to the present invention, the information processing apparatus 2100 provides the process result suitable for a profile of the user connected to the information processing apparatus 2100 through the Internet. [0326] The information processing apparatus 2100 according to the third embodiment includes at least one of a plurality of different image forming functions such as a printer, a FAX, and a copier, and also provides information concerning the image forming functions by a plurality of Web applications. In the third embodiment, for the sake of convenience, a case in that information concerning a copying process and a plotter for conducting a copy will be mainly described. [0327] A hardware configuration of the information processing apparatus 2100 is the same as that of the information processing apparatus 100 shown in FIG. 1, and explanation of thereof will be omitted FIG. 49 is a block diagram showing a functional configuration of the information processing apparatus according to the third embodiment of the present invention. In FIG. 49, the information processing apparatus 2100 is capable of connecting to terminals 2040 including a client PC 2041 used by a regular user, a client PC 2042 used by a system administrator, and a client PC 2043 used by another regular user, which require to display information corresponding to a profile. The information processing apparatus 2100 is a computer to provide information as a response with respect to a request sent from each of the terminals 2040. [0328] The information processing apparatus 2100 mainly includes a network controlling part 2101, a sequence control library 2110, a Web application distribution common library 2120, a Web page handler 2200, a SOAP (Simple Object Access Protocol) library 2201, an XML (extensible Markup Language) library 2203, an XSLT (XSL Transformations) processor 2205, a Web page function (WPF) 2300, a printer controlling part 2103, and a scanner controlling part 2105. [0329] The network controlling part 2101 includes at least an HTTP daemon 2002 for conducting a communication control in accordance with an HTTP (Hyper Text Transfer Protocol) The network controlling part 2101 receives the request from each terminal 2040 and provides information as a response with respect to the request. [0330] In order to execute a predetermined process so as to succeed to attribute information showing attributes concerning a utilization form of a Web browser of the terminal 2040 while a user conducts page transitions (browse one Web page linked from another web page) among a plurality of Web applications 2301, when the HTTP daemon 2002 receives the request from the terminal 2040, and additionally provides a temporary common path information, and a Web application ID and a CGI (Common Gateway Interface) which are referred to execute the predetermined process, to the URL indicated by the request. Similar to the first embodiment, the HTTP daemon 2002 adds necessary information and creates the URL formed by the common path information 60 a and the relative path information 60 b as shown in FIG. 3. The HTTP daemon 2002 additionally provides predetermined �/TERMINAL/PROFILE/LANG/webDefaultApl/default.cgi� to the URL [0331] The sequence control library 2110 is a processing part that is shared with the plurality of Web applications 2301 and handles by a predetermined sequence controlling process a difference between a process sequence of sending and receiving data through the Internet 2016 and another process sequence of sending and receiving data to/from each of the Web applications 2301. [0332] The Web application distribution common library 2120 is a processing part that is shared with the plurality of Web applications 2301, and that analyzes a request from the terminal 2040 and generates a response for the terminal 2040. The Web application distribution common library 2120 converts the response described in XML by the Web page handler 2200 into the response described in a display format by HTML (HyperText Markup Language) corresponding to the profile of the user using each terminal 2040 by using the XSLT processor 2205. [0333] The Web page handler 2200 is a processing part that converts a process language understandable for the Web applications 2301 into another process language understandable in the communication control conducted with the terminal 2040 for the request and the response. The Web page handler 2200 calls one Web application 2301 corresponding to the request via a CGI indicated by the request. Also, the Web page handler 2200 sends a serialization request to the SOAP library 2201 to serialize process result data provided from the Web page function 2300. [0334] Moreover, in the third embodiment, the Web page handler 2200 conducts an authenticating process for the user of the terminal 2040 by referring to an authentication information DB 2121. When the user is authenticated, the process result provided from the Web page function 2300 is provided based on the profile of the user The profile is a category of the user and shows an authorization level such as a regular user, a system administrator, a service person, and a like. For example, the user categorized as �administrator� is allowed to change network settings related to devices such as the plotter 35-1 or the scanner 35-2 (shown in FIG. 1). The user categorized as �regular user� is only allowed to display the network settings or cannot access information related to the network settings. The profile is used to determine a method for providing information. [0335] The authentication information DB 2121 manages a user name, a user password, a registered profile, and a like for each user. The registered profile shows the profile of the user when the user is registered. [0336] The SOAP library 2201 converts the process result data given by variables of C language into a description in XML so as to serialize the process result. In the third embodiment, serialization means to describe the process result provided from the Web page function 2300 in XML. [0337] The XML library 2203 is used by the SOAP library 2201 to serialize the process result by describing in XML. Also, the XML library 2203 is used by the XSLT processor 2205 to generate the process result described in HTML. [0338] The XSLT processor 2205 converts the process result described in XML into HTML by using the XML library 2203 based on a style sheet 2430 described in XSL (extensible Stylesheet Language) corresponding to the Web application 2301 indicated by the request from the terminal 2040. The style sheet 2430 is prepared beforehand by corresponding to each Web application 2301. [0339] When the Web page function 2300 is called from the Web page handler 2200, for example, inquires the printer controlling part 2103 or the scanner controlling part 2105 mounted to the information processing apparatus 2100 through an API (Application Program Interface) 2017, obtains information showing a status of a plotter 35-1 or a scanner 35-2 (shown in FIG. 1), and then provides the information to the Web page handler 2200. Moreover, the Web page function 2300 inquires the network controlling part 2101 through the API 2017, obtains information from the network controlling part 2101, and provides the information to the Web page handler 2200. [0340] Next, a detailed configuration for executing the Web applications 2301 will be described with reference to FIG. 50. FIG. 50 is a block diagram for explaining an execution of the Web applications according to the third embodiment of the present invention. In FIG. 50, for example, in order to provide information based on the configuration of the URL as shown in FIG. 3, the Web page handler 2200 includes an authentication handler 2205 executed to authenticate the user of the terminal 2040, a default handler 2210 executed at a first request from the terminal 2040 and at a role change request for requesting the Web page suitable for a higher profile like the administrator, a system status providing handler 2220 executed by the page transition in accordance with the instruction from the terminal 2040, a system configuration information providing handler 2230 similarly executed by page transition, and a like. [0341] Until an initial display screen is displayed at the terminal 2040, the default handler 2210 sequentially calls the Web default application 2310 through �default.cgi�, and then �netsetting.cgi� indicated by the page information 65 in accordance with the format of the URL shown in FIG. 3. As a result, for example, network settings of the device such the plotter 35-1 or the scanner 35-2 (shown in FIG. 1) mounted in the information processing apparatus 2100 are displayed at the terminal 2040. [0342] The system status providing handler 2220 calls a function for the Web system status providing application 2320 for providing information concerning the device mounted in the information processing apparatus 2100. In addition, the system configuration information providing handler 2230 calls the Web system configuration information providing application 2330 so as to obtain a system configuration information of the information processing apparatus 2100 in response to a request from the terminal 2040. [0343] In the same manner of the second embodiment, the Web application distribution common library 2120 executes each of the handlers 2210 through 2230 based on the Web information ID 64 of the URL shown in FIG. 3 by referring the hash lists 1050 a shown in FIG. 30A, and each of the handlers 2210 through 2230 executes the Web applications 2301 based on the page information 65 of the URL shown in FIG. 3 by referring the hash list 1050 b shown in FIG. 30B Also, in order to conduct the XSL conversion request which converts the process result described by XML to the XSLT processor 2205 into HTML, the Web application distribution common library 2120 selects the style sheet 2430 based on the page information 65 of the URL by referring to the hash list 1050 b shown in FIG. 30B. Therefore, detailed explanation thereof will be omitted. [0344] In the third embodiment, When the Web default application 2310 is executed through �rolechange.cgi�, the Web default application 2310 replaces the profile information 63 b in the common path information 60 a of the URL with the profile as the regular user. In this case, the default handler 2210 calls a function rolechange( ) based on �rolechange.cgi�, The Web application distribution common library 2120 selects the style sheet 2430 based on the page information 65 showing �rolechange.cgi�. For example, the style sheet 2430 is properly selected by �rolechange.xsl� corresponding �rolechange.cgi�. The Web application distribution common library 2120 executes the authentication handler 2205 by �authentication_handler� to authenticate the user of the terminal 2040 when the user requests the Web page for the higher profile. [0345] For example, when the user who is actually the system administrator of the terminal 2042 accesses the information processing apparatus 2100 as the regular user to display the initial display screen, in accordance with the process flows shown in FIGS. 31, 32, 37, and 38 similar to the second embodiment, the default handler 2210 sequentially calls the Web default application 2310 through �default.cgi�, and then �netsetting.cgi� to display the initial display screen at the terminal 2042, as described above. As a result, for example, the network setting page are displayed at the terminal 2042 as shown in FIG. 45 in the second embodiment. [0346] The network setting page in FIG. 45 in the second embodiment is the Web page for the regular user. Thus, the network setting page in FIG. 45 shows information concerning the network settings but the user of the terminal 2042 is not allowed to set or change the network settings. Since the user of the terminal 2042 is the administrator, the user requests the network setting page for the system administrator to the information processing apparatus 2100. That is, the user requests the network setting page for the higher profile. [0347] A process flow to change the Web browser corresponding to a desired profile of the user will be described with reference to FIG. 51 through FIG. 53. [0348]FIG. 51 is a diagram showing a process flow by rolechange.cgi according to the third embodiment of the present invention. In FIG. 51, the user of the terminal 2042 selects the network setting page for the system administrator from a menu showing a profile lists. In this case, a menu HTML for displaying the menu includes a script for each profile. For example, <a href=�/pc/admin/en/webDefaultApl/rolechange.cgi�>is described for the system administrator in the menu HTML. [0349] This script indicates that �rolechange.cgi� changes the profile information 53 b in a current common path information 60 a to �admin� showing the system administrator. [0350] When the user selects the network setting page for the system administrator, an HTML request changing a role is sent from the terminal 2042 to the information processing apparatus 2100 by indicating a URL of �/pc/admin/en/webDefaultApl/rolechange.cgi� (step S231). [0351] Based on �webDefaultApl/rolechange.cgi�, the default handler 2210 calls the function rolechange( ) so that the Web default application 2310 is executed. Then, the Web default application 2310 in the web page handler 2300 obtains profile information 53 b from the common path information 60 a of the URL and creates a URL to call the network setting page having the profile information 53 b showing �admin� (step S235). For example, �/pc/admin/en� is determined as the common path information 60 a and �/webDefaultApl/netsetting cgi� is determined as the relative path information 60 b. And the XSLT processor 2205 generates an HTML response having the URL calling the network setting page for the system administrator based on �rolechange.xsl�. The HTML response is sent to the terminal 2042. [0352] The HTML is not display at the browser of the terminal 2042 but automatically calls a HTML request displaying network settings with the profile information 53 b showing �admin� (step S240). [0353] The authentication handler 2205 includes an authentication determining part 2206 for determining whether or not the user is required to be authenticated based on the URL of the HTML request and an authenticating part 2208 for authenticating the user by referring the authentication information DB 2121. When the authentication handler 2205 is executed, the authentication handler 2208 obtains the profile information 53 b set in the URL and the determining part 2206 determines whether or not the profile information 53 b shows �admin� (step S243). [0354] In this case, since the profile information 53 b shows �admin�, the determining part 2206 determines that the user is required to be authenticated. Thus, the authentication handler 2205 sends an authentication request, that is, sends a predetermined �401 error� to require authentication information to the terminal 2042 (step S245) On the other hand, when the determining part 2206 determines that the user is not required to be authenticated, the authenticating part 2208 of the authentication handler 2205 executes the Web default application 2310 by calling the function �netsetting.cgi� (step S244). [0355] The terminal 2042 displays a password input screen to prompt the user to input the password of the user and sends an authentication response showing authentication information including the password input by the user to the information processing apparatus 2100 (step S250). Generally, a regular Web browser implements this authentication process sequence. It is not limited to this authentication process sequence but a special authentication screen can be formed and an original authentication process can be conduct. [0356] The authenticating part 2208 of the authentication handler 2205 conducts the authentication process to authenticate the user based on the password input by the user by referring the authentication information DB 2121. When the user is successfully authenticated, the authentication handler 2205 executes the default application 2310 through �netsetting.cgi� (step S255). [0357] After the process result is provided from the default application 2310, the network setting HTML for the system administrator is created based on the profile information 53 c showing �admin� and sent to the terminal 2042. [0358] Once the terminal 2042 accesses the information processing apparatus 2100 by the URL of �/pc/admin/en/webDefaultApl/rolechange.cgi�, �/pc/admin/en� is always succeeded while the user conducts the page transition. After that, the Web page provided from the information processing apparatus 2100 by the page transition can be the Web page for the system administrator. [0359] Next, a process flow conducted by netsetting.cgi from step S255 and step S270 will be described with reference to FIG. 52 and FIG. 53 in detail FIG. 52 and FIG. 53 are diagrams showing the process flow by netsetting.cgi according to the third embodiment of the present invention. In FIG. 52, the default handler 2210 of the Web page handler 2200 obtains the page information 65 showing �netsetting.cgi�, and specifies and calls the function netsetting( ) corresponding to �netsetting.cgi� (step S255) In this case, the HTTP connection information 2340 is set as an argument. [0360] For example, in a case in that the Web page function 2300 is developed by C language, the Web page handler 2200 converts into a process type of C language and calls the function netsetting( ). [0361] By executing the function netsetting( ) the Web default application 2310 requests information including a device name, a comment, and a like to the network controlling part 2101 through the API 2017, in order to display the status of a device (for example, plotter 35-1 as the printer) at the initial display screen (netsetting.cgi) (step S256-2). The network controlling part 2101 provides the information including the device name, the comment, and the like in response to the request (step S256-4). [0362] For example, the Web default application 2310 of the Web page function 2300 requests the status of the printer to the printer controlling part 2103 through the API 2017 (printer status request) (step S256-6) The printer controlling part 2103 provides the status of the plotter 35-1 as a printer status to the Web default application 2310 (step S256-8). [0363] Then, the Web default application 2310 provides the printer status, and the terminal type information 63 a, the profile information 63 b and the language information 63 c from the request URL 2354 of the HTTP request information 2350 as the process result data to the default handler 2210 in the Web page handler 2200 (step S257). [0364] In the following, the serialization process for describing in XML in steps S258, S259, S260, 3261, and 3262 is the same as the serialization process in steps S118, S119, S120, S121, and S122 in the second embodiment, and explanation thereof will be omitted. [0365] In order to convert the display data described in XML into a description of HTML corresponding to the profile of the user using the terminal 2042, the Web application distribution common library 2120 obtains the style sheet �netsetting.xsl� corresponding to the page information 56 showing �netsetting.cgi�, and conducts the XSL conversion request with respect to the XSLT processor 2205 (step S263). In this case, the display data �Response DOM� and the style sheet �netsetting.xsl� are set as arguments. When the XSLT processor 2205 receives the XSL conversion request, the XSLT processor 2205 executes the style sheet �netsetting.xsl� indicated in the argument. Accordingly, the XSLT processor 2205 selects one template corresponding to the profile from descriptions of the style sheet, analyzes a syntax of the display data �Response DOM� described in XML (parse XML), creates a DOM, additionally provides elements and attributes (step S264), and converts into the description of HTML by using the XML library 2203 (step S265). [0366] XSLT processor 2205 provides the description of HTML as the XSL conversion result to the Web application distribution common library 2120 (step S266). [0367] The process result described in HTML by the Web page function 2300 in a case in that the page information 65 is �netsetting.cgi� is output to the Web application distribution common library 2120 as a network setting HTML Information concerning the network settings of the plotter 35-1 is described in the network setting HTML. [0368] This network setting HTML response is provided from the Web application distribution common library 2120 to the sequence control library 2110 (step S267), and then is provided from the sequence control library 2110 to the HTTP daemon 2002 (step S268). Subsequently, the HTTP daemon 2002 sends the network setting HTML response as a response in accordance with HTTP with respect to the request sent from the terminal 2042 (step S269). Then, the process flow executed by �netsetting.cgi� is terminated. [0369] Values that can be set in the URL as the profile information 53 b will be describe with reference to FIG. 54 FIG. 54 is a diagram showing a correspondence between the profile information to set in the URL and the profile of the user according to the third embodiment of the present invention. In FIG. 54, �user� set in the URL shows that the user requests the Web page as the regular user, �admin� set in the URL shows that the user requests the Web page as the system administrator, �service� shows that the user requests the Web page as the service person, and a like. [0370] The authentication handler 2205 may send �401 error� if the profile information 53 c set in the URL is higher level than the profile of the user managed in the authentication information DB 2121. The authentication handler 2205 may determine whether or not the user is required to be authenticated. [0371]FIG. 55 is a diagram showing an example of the HTML response calling the network setting page for the system administrator according to the third embodiment of the present invention. In FIG. 55, an HTML response 2400 is not displayed at the terminal 2042, but a script 2401 that is Javascript� calls the network setting page. [0372] By a script 2402 showing �self.document.cookie=�cookieOnOffchecker=on; path=/��, information concerning the Web browser of the terminal 2042 is obtained. By a scrip 2403 showing �self.location.pathname=�/pc/admin/en/webDefaultApl/nets etting.cgi��, the profile information �admin� is succeeded, and the Web default application 2310 of the Web page function 2300 is executed. That is, a network setting HTML for the system administrator is requested. During a series of page transitions conducted by the user after that, an absolute path is indicated by a script 2403 as a reference for a relative path indicated by <a href> tag. [0373] The process result described in XML will be described. FIG. 56 is a diagram showing an example of the process result described in XML by netsetting.cgi according to the third embodiment of the present invention. [0374] In FIG. 56, an XML 2500 shows the process result when the user is successfully authenticated to change the profile information 53 c from �user� to �admin�. In an XML 2500 shown in FIG. 56, the process result by the function netsetting( ) of the Web default application 2310 is shown by a script 2501 showing from <networkResponse> to </networkResponse>. A script 2502 showing <terminal>pc</terminal> shows that the terminal 2042 is a personal computer, a script 2503 showing <language>en</language> shows that a language displayed at the Web browser of the terminal 2042 is English, and a script 2504 showing <profile>admin</profile> shows that the user of the terminal 2042 is the system administrator. The scripts 2502 through 2504 show information based on the terminal type information 63 a, the profile information 63 b, and the language information 63 c of the common path information 60 a of the URL A script 2505 showing <returnValue>SUCCESS</returnValue> shows that the network settings are successfully conducted. A script 2506 showing <ipAddress>999.999.999.999</ipAddress> shows that the IP address of the device (for example, the plotter 35-1) is �999.999.999.999�. A script 2507 showing <subnetMask>255.255.255.0</subnetMask> shows that the subnet mask is �255 255.255.0�. A script 2508 showing <hostName>Printer 1</hostname> shows that the name of the device is �Printer 1�. [0375] In the third embodiment, the Web page handler 2200 includes a function for serializing the process result data provided from the Web page function 2300 by describing in XML. Accordingly, each of Web applications 2301 of the Web page function 2300 is not required to include a processing part for describing the process result for each profile. [0376] The style sheet 2430, which converts the process result data described in XML to be serialized, into HTML by the XSLT processor 2205 based on the terminal type, will be described with reference to FIG. 57. FIG. 57 is a diagram showing a description example of the style sheet for converting the process result from XML to HTML according to the third embodiment of the present invention. [0377] In the style sheet 2430 shown in FIG. 57, it is determined by a script 2431 whether or not an element sandwiched with <terminal>tags shown by a script 2504 of the XML 2500 of FIG. 56 includes a character string �admin�, that is, it is determined whether or not the XML 2500 is the process result for the system administrator. A style sheet template for the system administrator is applied by a script 2432 when the character string �admin� is included. Another style sheet template for the regular user is applied when the character string �admin� is not included. The style sheet template for the system manager is described in a script 2434, and the style sheet template for the regular user is described in a script 2435. Details of each style sheet template are not shown in FIG. 57. [0378] When the terminal 2042 requests the network setting page for the system administrator, for example, the process result of the function netsetting( ) of the Web default application 2310 is described in HTML as shown in FIG. 58. FIG. 58 is a diagram showing a description example of HTML for the system administrator in that the process result of the netsetting.cgi is shown, according to the third embodiment of the present invention. In FIG. 58, HTML 2570 for the system administrator is provided to the terminal 2042 when the terminal 2042 requests the network setting page for the system administrator and the user is authenticated as the system administrator, and the process result of the function netsetting( ) of the Web default application 2310 is displayed at the Web browser of the terminal 2042 by scripts 2573 and 2575. [0379] The 2573 and 2575 are created based on the style sheet 2430 to display for the system administrator at the browser of the terminal 2042. The script 2573 is a script described in HTML for allowing the user input information concerning the network settings and send the information input by the user to the information processing apparatus 2100. The script 2575 is to link to one of other Web pages. [0380] By the script 2575, the network setting HTML can be linked to either one of two Web pages: �Browse System Status� page and �Browse System Configurations�. By a script 2576 showing>a href=�. . . /webSysstatusApl/sysstatus.cgi�>, �webSysstatusApl� as the Web application information 64 and �sysstatus.cgi� as the page information 65 are set as the relative path. When the �Browse System Status� page is selected by the user of the terminal 2042, the �Browse System Status� page is displayed at the terminal 2042 while a current language information 63 c is succeeded to by �. . . /�. In the same manner, By a script 2577 showing <a href=�. . . /webSysconfigApl/sysconfig.cgi�>, �webSysconfigApl� as the Web application information 64 and �sysconfig.cgi� as the page information 65 are set as the relative path. When the �Browse System Configurations� page is selected by the user of the terminal 2042, the �Browse System Configurations� page is displayed at the terminal 2042 while a current profile information 63 b is succeeded to by �. . . /�. [0381] The network setting page is displayed in English as shown in FIG. 59 by the network setting HTML in FIG. 58. FIG. 59 is a diagram showing the network setting page for the system administrator according to the third embodiment of the present invention. In a network setting page 2580 shown in FIG. 59, an input area 2584 and a selectable display 2585 are displayed at the terminal 2042 when the user of the terminal 2042 is successfully authenticated as the system administrator The input area 2584 is displayed based on the script 2573 in FIG. 58. The selectable display 2585 is displayed based on the script 2575 in FIG. 58. [0382] As described above, when the user conducts the page transition among the Web applications 2301, the profile information 53 c is automatically succeeded. Therefore, the user of the terminal 2040 is not required to indicate the profile of the user to request the Web page suitable for the profile. [0383] Moreover, in the information processing apparatus 2100, a consistency of creating the web page suitable for the profile of the user can be maintained among the Web applications 2301 in the Web page function 2300. In addition, each of the Web applications 2301 is not required to include a process for creating the Web page for each profile. [0384] Furthermore, the profile information 53 c is succeeded with respect to the request from each of the terminals 2040. Therefore, it is possible to display the Web page suitable for the profile of the user at the terminal 2040. In addition, the user is authenticated when the user changes the profile to display the Web page suitable for the profile. Accordingly, it is possible to protect information maintained in the information processing apparatus 2100 depending on the profile of the user. [0385] The present invention is not limited to the specifically disclosed embodiments, and variations and modifications may be made without departing from the scope of the present invention. [0386] The present application is based on the Japanese priority applications No.2002-212300 filed on Jul. 22, 2002, No.2002-242548 filed on Aug. 22, 2002, No.2002-242550 filed on Aug. 22, 2002, and No.2003-197850 filed on Jul. 16, 2003 the entire contents of which are hereby incorporated by reference. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7373347Jul 21, 2003May 13, 2008Ricoh Company, Ltd.Information processing apparatus and information processing methodUS8001551 *Apr 24, 2007Aug 16, 2011Microsoft CorporationProviding localized resources for client-side script executionUS8151184 *Aug 14, 2009Apr 3, 2012Arcadyan Technology CorporationMethod for promoting the accessing efficiency with embedded web pageUS8396990Apr 14, 2010Mar 12, 2013Afilias Technologies LimitedTranscoding web resourcesUS8433992 *Oct 28, 2009Apr 30, 2013Seiko Epson CorporationInformation distribution system, service-providing method for an information distribution system, and a program for the sameUS8504647Oct 20, 2009Aug 6, 2013Seiko Epson CorporationInformation distribution system, service-providing method for an information distribution system, and a program for the sameUS20100050071 *Aug 14, 2009Feb 25, 2010Arcadyan Technology CorporationThe method for promoting the accessing efficiency with embedded web pageUS20100107057 *Oct 28, 2009Apr 29, 2010Seiko Epson CorporationInformation distribution system, service-providing method for an information distribution system, and a program for the same* Cited by examinerClassifications U.S. Classification1/1, 707/999.1International ClassificationH04L29/06, H04L29/08Cooperative ClassificationY10S707/99932, Y10S707/99931, H04L67/02, H04L69/329, H04L69/22, H04L69/08, H04L67/306, H04L67/303, H04L29/06, H04L63/102, H04L63/083European ClassificationH04L63/10B, H04L63/08D, H04L29/06, H04L29/08N1, H04L29/08N29U, H04L29/08N29TLegal EventsDateCodeEventDescriptionSep 22, 2011FPAYFee paymentYear of fee payment: 4Nov 17, 2003ASAssignmentOwner name: RICOH COMPANY, LTD., JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:TAKAHASHI, SEIJI;KOBAYASHI, HIROKI;KOBAYASHI, SAYAKA;REEL/FRAME:014704/0209;SIGNING DATES FROM 20030902 TO 20030904RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services