KR20020048229A - Mixed contents server-client system - Google Patents

Abstract

PURPOSE: A server-client system for the mixed contents is provided to offer the static contents, the dynamic contents and a GUI(Graphic User Interface) program to a client. CONSTITUTION: The client(110) and a mixed contents server(150) are connected through a network. The mixed contents server includes an application program supporting server(160) capable of simultaneously operating the GUI application program of many users and transferring the screen to the client and a web/servlet server(170) carrying out a function confronting to the usual web server. In the mixed contents server-client system, all programs are executed on the server side and the clients only carry out the function for displaying the screen transferred from the server and transferring the user input to the server.

Description

Mixed Content Server-Client System {MIXED CONTENTS SERVER-CLIENT SYSTEM}

The present invention relates to a server-client system, and more particularly, to a hybrid content server that simultaneously provides a thin client and an application and content to the thin client.

As services based on the Internet have been expanded, there is a need for a technology that enables various types of services. 1 is a block diagram illustrating a server 50-client 10 system for providing a conventional web-based service. Existing web server 50 can be dynamically generated by static content (static Hypertext Markup Language (HTML) file, 54) or dynamically generated content (common gateway interface (CGI), servlet (56, 58), etc.). It is structured to provide the generated HTML]. In the system of FIG. 1, a service is provided by a client's browser 12 interpreting and displaying static or dynamic HTML content provided by a server 50 on a screen and transmitting user input to the server.

However, as shown in FIG. 1, since a user interface using a browser has many limitations in operation as compared with a general GUI (Graphic User Interface), it is difficult to apply to various applications such as a game or a chat. In addition, even if applicable, the entire page must be newly drawn when data exchange with a web server is required, so it is very inefficient when only a part of the screen needs to be changed. Therefore, for such an application, it is common to have a program made in the form of an applet or an ActiveX on the server side 50 and download it to the client 10 to be executed on the client. Such a program is separately connected to the server's database 60 or the like for data exchange with the server (see connections 13 and 60 of FIG. 2). FIG. 2 illustrates a state in which the server 60 is connected to the database 60 using the Java applet 13 downloaded from the web server 52 in the conventional server-client environment.

The system of the type shown in FIG. 2 has several disadvantages.

First, in order to execute an application in the client 10, a Java applet or ActiveX and necessary libraries have to be downloaded from the server 50, so the user's waiting time is long.

Second, compatibility may be inferior depending on the client environment [OS version, version of Java Virtual Machine (JVM), browser] and the application may not be executed.

Third, there are two paths for accessing the database 60 via the web server 52 and the case in which the applet 13 directly connects, making it difficult to manage or write an application program.

Fourth, ActiveX has various security problems, and even Java applets cannot be used unless they are separately authenticated if the database is located on a web server and another server.

In addition, when using a separate stand-alone application or Java applet, there was a problem that the linkage with the web server, linkage with other content based on HTML is not well achieved.

Accordingly, an aspect of the present invention is to provide a mixed content server and a corresponding client system that can provide static content, dynamic content, and GUI applications to a client in one server.

Another object of the present invention is to provide a server and client system supporting a hyperlink between services in various modes, and a data transfer method therefor.

Another object of the present invention is to provide a method for supporting hyperlinks between GUI / application and dynamic / static content of the same server or another server.

Another object of the present invention is to simplify the client terminal in the server and the client system to handle only simple input and output.

1 shows an example of a conventional client device comprising a browser and a conventional server comprising a web server.

2 is a diagram illustrating a case where a Java applet is used in a conventional client device including a browser and a conventional server including a web server.

3 is a diagram illustrating an environment in which a hybrid content server and a client device according to the present invention are used.

4 is a block diagram of one embodiment of a hybrid content server in accordance with the present invention.

5 is an internal block diagram of one embodiment of a client device in accordance with the present invention.

6 is a program structure diagram of an embodiment of an application support server (TAP server) included in a hybrid content server according to the present invention.

7 is a diagram illustrating an embodiment of a process of generating and transmitting graphic data in a hybrid content server according to the present invention.

<Explanation of symbols for the main parts of the drawings>

10, 20, 30: client

50: server

110, 120, 130: Mixed Content Client

150: Mixed Content Server

160: application support server unit

170: web / servlet server unit

According to an aspect of the present invention, there is provided a server device to which a plurality of clients can connect, comprising: first server means for executing one or more GUI application programs and transmitting image information of each program to a client side;

Second server means for providing content

There is provided a server device comprising a.

The GUI application program includes a browser, and the contents of the second server means are provided to the client side through the browser.

According to another aspect of the present invention, there is provided a first server means for executing at least one GUI application program including a browser, and transmitting image information of each program to a client side, and second server means for providing contents. A method for providing contents of one of the servers to one of the clients when the at least one server and the at least one client are connected through a network,

Receiving a content providing request of a second server from a client at the first server;

In response to the request, the browser included in the first server means of the first server reading and interpreting the content of the requested second server from the second server means of the second server;

And providing, by the first server means of the first server, the image information of the browser screen formed by analyzing the content to the client.

According to another aspect of the present invention, one or more first server means for executing one or more GUI application programs including a browser, and transmitting image information of each program to a client side, and one or more agents for providing contents. 2 server means and a method for operating said first server means when at least one client is connected via a network,

Receiving a first server connection request from a client, the first server connection request including a request for an application program;

Executing the application program included in the first server means in response to the request;

And providing, by the first server means, the image information formed by executing the application program to the client.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

3 is a diagram illustrating an environment in which a hybrid content server and a client device according to the present invention are used. As shown in FIG. 3, the clients 110, 120, and 130 and the hybrid content server 150 according to the present invention are connected through a network. The client 110, 120, 130 is a device that receives a user's input and delivers it to the server 150 and delivers the output of the server to the user as a screen or sound, and operates in a software or web browser that operates on the existing PC 110. Applet, software for PDA 120, the mobile phone 130, etc. may be in the form of software or a dedicated terminal device. The server 150 may be configured as a general server computer in terms of hardware. The server 150 includes an application support server unit 160 and a web / servlet server unit 170. The client and server are connected by any network 140 capable of 1: 1 communication, such as TCP / IP.

4 is a block diagram illustrating an embodiment of a hybrid content server 150 according to the present invention. The hybrid content server 150 according to the present invention is an application support server unit 160 and a conventional web server unit having a function of simultaneously operating GUI applications of multiple users and transmitting the screens to the client 110. And a web / servlet server unit 170 that performs a function corresponding to (reference numeral 52 of FIGS. 1 and 2). In the following, the application (or tapplet) refers to unique application software that runs on the hybrid content server 150 of the present invention, rather than a conventional general application that runs on a PC or workstation, for example. Unlike CGI, it refers to a GUI application program that has its own user interface (display). In the server-client system of the present invention, the programs are all executed on the server side, and the client 110 performs only a function of displaying a screen received from the server and transmitting a user input to the server. The support server unit 160 and the client 110 will be described later with reference to FIGS. 5 to 7.

In FIG. 4, the application programs 1 and 2 included in the support server unit 160 are GUI applications operating in the hybrid content server 150 of the present invention as described above. The browser 440a is a kind of application according to the present invention and includes an HTML or a wireless application protocol (WAP) browser.

The path 1 shown in dotted lines in FIG. 4 represents an operation in which the client 110 requests the server to execute the application program 440a, and as a result, receives and displays a screen. The path 2 indicated by the dotted line in FIG. 4 is a case where the address required by the client designates an HTML file 176 that exists in the server 150. The path 2 automatically executes the browser 440a to retrieve the HTML file of the address. After reading and interpreting, the resulting screen is transmitted to the client 110. The path (3) is similar to the path (2) but does not specify a static HTML file, but rather a servlet 172 included in the web / servlet server unit 170 so that the resulting HTML content is The case in which the screen generated by the browser 440a and interpreted by the browser 440a is transferred to the client 110 is illustrated. The application support server unit 160 may be implemented in Java, and the servlets 172 and 174 may be replaced by CGI in the web / servlet server unit 170. When the web / servlet server unit 170 is implemented in Java, for example, the web / servlet server unit 170 may be configured to be executed in a JVM (Java virtual machine, 410 of FIG. 6) such as the application support server unit 160 due to efficiency. It is not.

Although only one server 150 is illustrated in FIGS. 3 and 4, a plurality of such servers 150 exist on a network, and thus, in the server client environment of the present invention, a client may be connected to a hyperlink used in a web (WWW). In a similar manner it is possible to surf freely while accessing multiple hybrid content servers connected on a network. This is similar to conventionally freely accessing multiple web servers connected on the Internet through a web browser.

5 is a diagram illustrating a configuration of an embodiment of a client device according to the present invention. Description of the thin client and the application support server unit 160 according to the present invention described with reference to FIGS. 5 to 7 is 2, 4 of the application No. 2000-64551 dated November 1, 2000, designed by the same inventor. And the description of the thin client and server with reference to FIG. 5. The structure of the server program described in the application 2000-64551 is a preferred embodiment of the configuration of the application program support server unit 160 according to the present invention, but the support server unit 160 of the present invention is not limited thereto.

In FIG. 5, the screen 210 is a general bitmap display device. The keyboard 240 may be a keyboard of a general PC, a character input device by a pen used in personal digital assistance (PDA), or may be composed of a limited number of keys as in a mobile phone. Pointing device 250 is a device that can input the position of the mouse, pen, and the like. When a user input is detected by the keyboard 240 and the pointing device 250, it is transmitted to the server side on the network via the transceiver 260 of the client. The image reconstructor 220 may use the offscreen buffer 230 as a device or software for displaying the compressed image transmitted from the server side to reduce flickering of the screen or to improve compression efficiency. Certain types of graphical operations may be passed from the server side in the form of operation codes rather than images, such that the results of these operations may be applied to screen 210 or offscreen buffer 230.

The transmitter / receiver 260 transmits a user input from the keyboard 240 or the pointing device 250 to the server side, and receives screen information from the server side. The transceiver 260 may include a wired / wireless modem.

6 shows one embodiment of the configuration of the application program support server unit 160 that operates on the server computer. In a preferred embodiment of the present invention, the application support server 160 is operated by one JVM 410, but is not limited thereto. When a new client connects, a new user session is created on the support server. A plurality of user applications 440a, 440b or 440c, 440d may be driven in one user session. As described above, the application is a GUI application used in the server-client environment of the present invention and includes a browser 440a in accordance with the present invention. In order to update the screen of the client side 110, the support server 160 intercepts the screen output of this application program and transmits the compressed data of the graphic operation code or the resultant image to the client 110. The user input from the client 110 is transmitted to the user application 440 through the system's event queue as if the user had input directly using the keyboard and mouse at the console of the server computer 150. do.

The state of a user session can be stored in a database or file system (not shown) on the server side when the connection between the client and server is terminated, and then loaded into a newly created user session when the connection with the server is resumed. have. By doing this, the client side can always start work in the last working state even if the device is turned on and off at will. In addition, even when a client repeatedly accesses one or more servers, returning to a given server can immediately return to a previous working state.

Hereinafter, the application program support server unit 160 shown in FIG. 6 will be described in detail.

In a preferred embodiment of the support server unit 160 according to the present invention, a thread and an event queue for event processing are separately provided for each user session in order to minimize the influence between applications used by different clients. Is assigned. This is different from the prior art, where there is usually only one event thread and queue per JVM.

When the new client connects, the session manager 420a creates a new session. If there is no communication from the client for some time, the session manager 420a determines that the connection with the client is stopped, and deletes the session.

The application manager 420b includes a list of applications that are executed in the client-server system of the present invention. In an embodiment of the present invention, different applications can be accessed according to a user. For example, it is possible to divide a user into a paid user and a free user so that only the paid user can use various kinds of applications, and the free user can use only a few test applications.

The image compression library 420c includes software components used to compress the image data to be displayed on the client side, as described below.

The AWT lightweight component library 420d is a set of lightweight components, such as buttons, text fields, scroll bars, etc., which is implemented in the environment of the present invention rather than in the standard library of Java.

When the client accesses the session manager 420a shown in FIG. 6, a new session is created. One ZAppletContext object 460 is created for each session. Each ZAppletContext contains an event queue, a thread for processing input from the client, a thread for processing GUI events, a client screen buffer, and an offscreen buffer. Hereinafter, each of them will be described in detail.

Event queue: A general Java application has one event queue in the entire JVM, but the server of the present invention has an event queue for each session so that programs of each user can operate independently.

A thread that handles input from the client. Receives event input from the client's keyboard and pointing device and puts it on the event queue.

Thread for handling GUI events: When a new event comes in the event queue, it performs a task registered in advance by the application.

Client screen buffer (550): The buffer holding the contents of the last screen of the client. It is used to calculate the difference with the previous screen when compressing and transferring the newly displayed screen.

Off Screen Buffer 540: Has a copy of the application screen. In general, off-screen buffers are used for double buffering to prevent flicker of the screen, but the server of the present invention is used for direct access to image data.

When the client connects to the server, the client sends information about the screen size of the client device to the server side, and the size of the client screen buffer 550 and offscreen buffer 540 is determined to be equal to the screen size of the client device by this information. All. Similarly, the depth of the client screen buffer and offscreen buffer (bits per pixel) is set to be equal to the screen depth of the client device.

As shown in FIG. 6, the application takes the form of a Java applet, but inherits the ZApplet class 450 defined in the present invention instead of the applet class inherited by a general applet. The Gapplet overrides the applet's getGraphics () function so that all graphics operations in the application are done through the ZGraphics object (520 in FIG. 7). Each application executed on input from the client is implemented as a new class inherited from the Gapplet class.

7 is a diagram illustrating a process of updating and transmitting screen information according to an operation of an application in a preferred embodiment of the present invention. First, when an application program needs to be updated as a result of a predetermined operation, a graphic operation is performed through the ZGraphics object 520 (1). In the next step, the result of the graphic operation is drawn in the physical window 530 of the server (2) and also in the off-screen buffer 540 (3).

According to one embodiment of the present invention, in order to minimize the amount of data to be transmitted to the client 110 to update the screen, as described below, a method of simultaneously transmitting the operation code and the differential image data. That is, a small amount of parameter during the graphic operation but a large change in the screen, for example, a block copy of the bitmap during scrolling of the screen, is applied to the client screen buffer 550 (4) and simultaneously to the client. Passed in the form of code. It is well known that an operation code can be represented by a very small amount of data.

When the screen update process of the application is completed, the difference between the offscreen buffer and the client screen buffer up to this point is calculated (5). The difference is compressed and transmitted to the client 110 together with the operation code (6). The difference is compressed by the image compression unit 560 using various known image compression methods or encoding methods.

Alternatively, in another embodiment of the present invention, the original image that is not the difference may be transmitted to the client, or the difference or original image may be selectively compressed and transmitted to the client. At this time, the criterion of which of the difference and the original image to be sent may be to compress both of them and to send the more efficient one. It is also possible for the application to determine this and notify the session object (ZAppletContext).

When the transfer to the client 110 is completed, the contents of the offscreen buffer are copied to the client screen buffer (7), and the contents of the client screen buffer are updated with the latest data.

The physical window 530 is used for monitoring, but is not necessary for the operation of the client. Thus, the number of clients that can be omitted and concurrently connected is not limited by the actual window size.

5, the process of updating the screen on the client side is as follows. The client receives the operation code and the compressed differential image information from the server through the transceiver. The image reconstruction unit 220 on the client side restores the compressed image information. Also, a graphic operation corresponding to an operation code is performed on previous image information stored in a video memory (not shown) on the client side. Thereafter, the restored difference image is added to the image information after the graphic operation is performed and displayed. Alternatively, in order to prevent flickering, the above process may be applied to a separate off-screen buffer (FIGS. 5 and 230) and copied to video memory at once.

Returning to FIG. 7, since all graphic operations are performed through the ZGraphics object 520 in one embodiment of the application supporting server 160 according to the present invention, the ZGraphics object 520 may know the boundary of the changed area of the screen. have. This information can be used to find the difference and limit the area of the screen that is sent to the client.

In addition, the method of writing a general GUI program often makes a new drawing every time even the portion of the screen which does not change. In this case, in order to prevent unnecessary retransmission, the contents of the actual window 530 and the offscreen buffer 540 may be compared to obtain only the changed region.

GUI components (lightweight components such as buttons, text fields, etc.) use implementations that are tailored to the environment of the present invention, not in the Java standard library. These components may be displayed in an appropriate form depending on the screen resolution or depth of the client device. For example, a black and white screen may display a border of a button as a simple line, but a client having high resolution and color support may display a three-dimensional effect differently. This display adaptation is made according to the screen of the client device for each session irrespective of the actual screen of the server of the present invention.

In the present specification, it has been described that one session is generated per one client, but it is also possible to have two or more clients connected to one session. In this case, more than one client may work remotely.

4, an example of the browsing operation in the server-client system shown in the drawing will be described according to the time flow of the operation.

1. At the client 110, a user specifies a server address. For example, specify "foo.com".

2. The client 110 connects to the designated port of the foo.com server and requests "/".

3. The application support server unit 160 searches for "index.html" which is designated as the default content of the "/" directory, and has an extension of "html". Therefore, the "/index.html" browser is executed while executing the browser 440a. "As an argument.

4. The browser 440a reads and interprets "/index.html" and transmits the completed screen to the client 110. This screen contains a list of icons for various content and applications, for example, from the foo.com server.

5. For example, a user clicks an icon representing "mail" on a client screen (not shown), and the coordinates of the clicked icon at this time are transmitted to the support server unit 160. The server sends a mouse event back to the browser 440a.

6. The coordinates corresponding to the mouse event in the "/index.html" file that the browser 440a is currently displaying are, for example, <a href="tapplet:/foo.com/app/mail"> <image src = It connects to "/ app / mail" on server "foo.com" like "images / mail.gif"> </a>. The browser calls the goto () function of the session object it contains (ZAppletContext, 460a) with the "/ app / mail" argument. The goto () function is a function for moving to an application or HTML content, which is given as an argument, and performs other operations in some cases (depending on the origin and destination of the movement) as described below.

7. In the session object, stop the currently running browser and run the application specified by "/ app / mail". The resulting screen is transmitted to the client 110.

8. The user runs the mail application and executes the "back" function of the client.

9. The "back" command is sent to the server 150 and received by the session object to stop the mail application and relaunch the previously running browser.

10. This time, for example, the user selects the "news" icon in the browser. This icon looks like the <a href="/servlet/news.class"> <image src = "images / news.gif"> </a> in the "index.html" file. )

11. When the browser requests "/servlet/news.class" to the web / servlet server unit 170 by the HTTP protocol, the web / servlet server unit 170 executes the /servlet/news.class servlet 172. The resulting HTML code is passed to the browser 440a.

Next, the hyperlink between the applications 440a and 440b and the HTML / servlet of the web / servlet server unit will be described. In particular, providing a platform that supports hyperlinks between applications and HTML / servlets is one of the main features of the hybrid content server of the present invention.

First, the hyperlink from the application 440b to the HTML 176 will be described. In order for the application 440b to display a specific HTML file 176 or servlet 172 on the screen when a button is pressed, for example, the session object 460a of the session 430a to which the application 440b belongs. ) Is called with the URL (the URL pointing to the HTML or servlet) as the argument to the goto () function. At this time, the goto () function temporarily stops the currently executing application 440b, executes the browser 440a, and opens a corresponding URL page.

Second, the link between the application programs will be described.

For example, when an application 440b causes another application to be executed when a button is pressed, the operation is different when two applications are located in the same server and when they are located in different servers.

1. If the linked application 440c is located within the same server

Step 1. The goto () function of the session object of the session to which the original application 440b belongs is called with the name of the linked application 440c.

Step 2. The session object stops the currently running application 440b and executes the given application 440c.

2. The linked application is located on a different server

Step 1. Call the goto () function of the session object of the session the application belongs to with the name of the linked application. However, this name also includes the name of the server to be moved. For example, "tapplet: //foo.com/app/mail".

Step 2. The session object sends a "goto foo.com:/app/mail" command to the client and terminates the connection with the client.

Step 3. The client connects to the foo.com server and requests to run / app / mail.

At this time, as described above, when the client's creation state is stored in each server, for example, by pressing the "back" button during the execution of the mail, the application program used in the original server can be returned.

Third, the link from an HTML file to another HTML file is based on the general hyperlink method on the web. At this time, the currently connected application program support server unit and the running browser are kept connected and running. In other words, even when a link is moved from an HTML file of one server (first server) to an HTML file of another server (second server) by using a link, the application support unit and the running browser of the first server continue to connect with the client. And keeps running. However, the application program support unit of the first server accesses the second server through a browser, reads and parses the HTML file of the web server unit of the second server, and transmits the result screen to the client side.

Fourth, we will discuss the connection from HTML to the application.

The application is specified by the <a href="tapplet://...."> tag. The "tapplet: //" approach suggests one protocol for "http: //", but unlike "http: //", it is not yet standardized. "tapplet: //" is recognized in the server-client system according to the present invention, and the browser operating in the server unit recognizes this and extracts the name of the tapplet designated in the tag. Subsequently, the application is driven in the same manner as the link from the application to another application (tapplet) described above.

Next, parameter passing by URL will be described.

As is known, the parameters can also be marked when invoking a tapplet according to the present invention, as can be indicated together after the URL of a servlet or CGI. For example, the URL of a web mail that conventionally displays a user's mail

<a href="http://mail.foo.com/mail?userid=aaaa"> Mail </a>

As can be expressed as follows, a user ID can be given as a parameter to a URL for calling an application program for viewing a mail among the tapplets according to the present invention as follows.

<a href="tapplet://mail.foo.com/mail?userid=aaaa"> Mail </a>

Thus, according to the present invention, it is possible to implement a server-thin client system in which most operations take place on the server side. At the same time, a very simple hardware client allows users to freely use and view applications and content in a manner similar to conventional web browsing.

The present invention is a thin client-mixed content server technology developed for the purpose of performing various application programs and content views in a portable device. The hybrid content server of the present invention may be executed on any server computer equipped with a JVM, for example in the form of a Java application. The client of the present invention can be ported to a variety of portable devices with graphical display and keyboards (or other input devices) and pointing devices.

While the specification has been described with respect to specific embodiments, it will be apparent to those skilled in the art that other variations and modifications are possible.

For example, it is possible for the hybrid content server or client of the present invention to have a configuration other than that illustrated herein. Each application support server can also be implemented using a variety of different methods and tools. Accordingly, it is to be understood that all such modifications and variations are included in the spirit of the present invention as defined in the appended claims.

The server of the present invention simultaneously provides an application and content and is accessible in a hyperlink manner as in a conventional web server. On the other hand, all operations are performed on the server side, and only screen information is transmitted to the client side. Therefore, from the user's point of view, various applications and contents can be used only with a very simple terminal device, and since the hyperlink method is used, it is very easy to use. The user can use various programs and contents at a low cost without the cost of installing and maintaining the program, and only the screen information or user input is transmitted without having to download a complicated program to the client every time. This can be reduced compared to using an application service provider (ASP).

Claims (13)

A server device to which a plurality of clients can connect, First server means for executing at least one GUI application program and transmitting image information of each program to a client side; Second server means for providing content Including, The GUI application includes a browser, And the contents of the second server means are provided to the client side through the browser. The method of claim 1, wherein the first server means One Java virtual machine, Includes a plurality of client sessions operated by the one Java virtual machine and A server device in which each session runs one or more applications corresponding to each client. The server apparatus of claim 2, wherein each of the sessions provides image information to be displayed on the client. 3. The server apparatus according to claim 2, wherein said first server unit comprises means for providing image information to be displayed on each client, said image information including an operation code and differential image information. The server apparatus of claim 1, wherein the content comprises at least one of static content in the form of an HTML file and dynamic content in the form of a CGI or servlet. The server apparatus according to claim 1, wherein when the client requests predetermined contents, the browser interprets the contents in the second server means in response to the request, and transmits the image output to the client as a result. . At least one server and at least one client, including at least one server for executing at least one GUI application program including a browser and transmitting image information of each program to a client side, and at least one second server means for providing content. A method for providing content of one of said servers to one of said clients when connected via a network with a network, Receiving a content providing request of a second server from a client at the first server; In response to the request, the browser included in the first server means of the first server reading and interpreting the content of the requested second server from the second server means of the second server; Transmitting, by the first server means of the first server, the image information of the browser screen formed by analyzing the content to the client. Content providing method comprising a. The method of claim 7, wherein the first server and the second server are the same server. The method of claim 7, wherein the first server and the second server are different servers. At least one first server means for executing at least one GUI application program including a browser, and transmitting image information of each program to a client side, at least one second server means for providing content, and at least one client A method of operating said first server means when connected via a network, Receiving a first server connection request from a client, In response to the request, the browser included in the first server means reading and interpreting predetermined content from the second server means; Transmitting, by the first server means, the image information of the browser screen formed by analyzing the predetermined content to the client. Operating method comprising a. The method of claim 10, wherein the predetermined content includes a plurality of hyperlinks, and wherein the plurality of hyperlinks include hyperlinks to one or more application programs of the one or more first server means. The method of claim 10, wherein the predetermined content includes a plurality of hyperlinks, and wherein the plurality of hyperlinks include hyperlinks to one or more contents of the one or more second server means. At least one first server means for executing at least one GUI application program including a browser, and transmitting image information of each program to a client side, at least one second server means for providing content, and at least one client In the method of operating said first server means when connected via a network, Receiving a first server connection request from a client, wherein the first server connection request includes a request for an application program; Executing the application program included in the first server means in response to the request; Transmitting, by the first server means, the image information formed by executing the application program to the client. Operating method comprising a.