JP2000122871A - Application distribution method - Google Patents

Abstract

(57) [Summary] [Problem] To provide an application in a format suitable for various clients, a large number of applications must be prepared, which is complicated for both the provider and the user. A client downloads an application via a proxy server. The proxy server receives the application request and obtains the application from the application server on behalf of the client. The proxy server converts the application into a format suitable for the client and sends it to the client.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a method of distributing an application in use of a computer.

[0002]

2. Description of the Related Art With the development of networks and the spread of terminals, a system for distributing applications widely has been required. Currently the most common method is
This is a method of distributing applications using a Web server. For details on the web server, see "Nancy J. Yeager / Robe
rt Web Server Technology-The Advance by McGrath
dGuide for World Wide Web Information Providers ''
It is described in. The feature of this method is that the application can be downloaded from anywhere as long as it can be connected to the Internet.

[0003]

The application distribution method using a Web server is simple and efficient, but it is difficult to cope with some complicated situations. Client architectures vary widely. There can be several versions of the same architecture. To serve many clients, you have to provide many load modules for one application.

[0004] A user must search for a module suitable for his terminal from among many load modules. Users are not necessarily familiar with computer architecture, so they have a lot of trouble.

Some applications are distributed in source code or virtual machine code. Compiling the source code is extremely complicated.
Users who do not have a compiler in the first place cannot compile code. In order to execute virtual code, a virtual machine must be installed on a terminal. This is also a complicated operation. Depending on the type of terminal, it may not be possible to install a virtual machine.

[0006]

Means for Solving the Problems A client downloads an application via a proxy server.
The proxy server receives the application request and obtains the application from the application server on behalf of the client. The proxy server converts the application into a format suitable for the client and sends it to the client.

[0007]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1 shows the overall configuration. The user is connected to the client terminal 103 connected to the network.
From the application server 102 via the compile server 101. The target from which the application is downloaded may be the client terminal 103 itself, or another mobile terminal 104. The user first connects to the compile server 101, and from there the server 10 that distributes the desired application
Access 2 The application server 102 may be on the same host as the compile server 101, or may be on another host on the network.

[0008] A request from a client first reaches the compile server 101. From there application server 1
02, the request is forwarded, and the application is sent as a response. The compile server 101 compares the format of the application with the architecture of the client, executes appropriate conversion processing such as compiling, and transmits the result to the client.

FIG. 2 is a diagram for clarifying the processing flow. First, an application request 202 is transmitted from the client 103 to the compile server 101. At this time, the client information 201 is added and transmitted. The method of adding the client information depends on the client. Many Internet browsers send requests with client information added. If the default information is not enough, you can request the information from a proxy server. See Nancy J. Yeager / Robert E. McGrat for details.
h Web Server Technology-The Advanced Guide for
World Wide Web Information Providers ".

The compile server 101 sends the application request 203 to the application server 102 after storing the application request 202 and the client information 201 in a list. The application server 102 sends the appropriate application 204 to the compile server 101 as requested.

The compile server 101 compares the sent attribute of the application 204 with the stored client information 201 and selects an appropriate conversion process. The compile server executes a conversion process by activating a compiler or a linker. Details of the processing will be described with reference to FIG. When the processing is completed, the converted application 205 generates the application. The compilation server 101 executes the converted application 205
Is transmitted to the client 103 as a response.

FIG. 3 shows the configuration of the compile server 101. First, there is a unit 301 for controlling the whole.
The client request table 302 and the client information table 304 will be described later in detail. The compiler 306 and the library 307 compile the application and generate a load module suitable for the client. In addition, linkers and virtual code native compilers may be added. The communication interface 308 communicates with a client or an application server.

FIG. 4 shows the structure of the client information table 304. The client information table 304 is a table prepared in the compile server 101 in advance. The client information table 304 includes a record 305 having a client type 401 and a compile command 402 as items. Client type 401
Is an identifier that literally identifies the client's architecture. In many implementations, the model and model of the terminal will be stored. Compile command
Reference numeral 402 stores a command for converting an application into a format suitable for a client. The compile server 101 refers to this item and executes appropriate conversion processing such as compiling and linking.

FIG. 5 shows the structure of the client request table 302. The record 303 of the client request table 401 is created each time a request is received from a client, and is deleted when a response is returned to the client. The client request table 302 includes a record 303 having a client type 501 and a request application 502 as items. The client type 501 stores information transmitted from the client together with the application request 202. Used to identify the architecture of the client. In many implementations, the model and model of the terminal will be stored. The request application 502 is for remembering the application requested by the client. In many implementations, application requests 202 will be stored.

FIG. 6 is a diagram showing a procedure in which the compile server 101 receives a request from the client 103 and issues a request to the application server 102. First, at 1601, a request is received from the client 103. Search the client information table 304 at 602, and
3. Determine the search result. If there is no item corresponding to the client, it means that application conversion corresponding to the client cannot be performed. Transfers control to 604, returns an error to the client, and ends. The compile server 101 itself shifts to a state of waiting for the next request.

When an item corresponding to the client is found, the process proceeds to 605, where a request is registered in the client request table 302. Next, at 606, an application request 203 is transmitted to the application server 102, and a response is awaited.

FIG. 7 is a diagram showing a procedure in which the compile server 101 receives a response from the application server 102 and transmits the response to the client 103. 701
Receives a response from the application server or 102,
The format of the sent application 204 is checked. 702
Then, the client request table 302 is searched to determine which client responds to the request. At 703, the search result is determined. If it is not a response to the registered request, control is transferred to 704 and an error is returned to the server. If registered, control is transferred to 705 to check the client type. Further, by pulling the client information table 304, a conversion command (compile command) 402 corresponding to the client is obtained. The compile server 101 executes this command to obtain an application 205 in a format suitable for the client. In most cases, it is in the form of a load module. Load module to client 103 at 706
Send 205 and end the session.

FIG. 8 shows a process when the source application 801 is received as the application 204. The compile server 101 checks the client information table 304 and obtains a compile option. Compiler 3 using the option obtained earlier as an argument in 802
06 is started, and the source code 801 is compiled into the load module 803. The generated load module 803 can be directly executed by the client.

FIG. 9 shows a process when the application 901 in the object format is received as the application 204. Object-based application 90
1 can be executed as it is on the client, but often cannot be executed without linking the library specific to the machine. At 902, the compilation server 101
The client command table 304 is checked to obtain a link command. The command activates the linker 309, links the machine-specific library 307, and generates the load module 903.

FIG. 10 shows processing when the application 1001 in the virtual code format is received as the application 204. If the client has a virtual machine installed, the virtual code can be executed as is. Otherwise, it cannot be executed on the client unless it is converted to a load module. At 1002, the compile server 101 checks the client information table 304 and obtains a conversion command. The compilation server invokes a converter or compiler 306 to generate the virtual code 100
Convert 1 to a code 1002 in a format suitable for the client.

[0021]

As described above, according to the present invention, the client does not need to be aware of the format of the application.
Can be downloaded.

[Brief description of the drawings]

FIG. 1 is an overall configuration diagram illustrating distribution of an application according to an embodiment of the present invention.

FIG. 2 is a diagram showing an application distribution procedure of FIG. 1;

FIG. 3 is a view showing a processing procedure of a compile server in FIG. 1;

FIG. 4 is a diagram showing a configuration of a client information table of FIG. 3;

FIG. 5 is a diagram showing a configuration of a client request table of FIG. 3;

FIG. 6 is a flowchart showing a procedure from when a compile server receives a request until it issues a proxy request.

FIG. 7 is a flowchart showing a procedure from when a compile server receives a response to when it transmits the response to a client.

FIG. 8 is a flowchart showing processing when the compile server receives a source format application.

FIG. 9 is a flowchart showing processing when the compile server receives an application in an object format.

FIG. 10 is a flowchart showing processing when the compile server receives an application in a virtual code format.

[Explanation of symbols]

101: compile server, 102: application server, 103: user PC, 104: portable terminal.

Claims (1)

[Claims] In a network system, an application receives an application request from a client, obtains an application from a server on behalf of the client, converts the application into a format suitable for the client, and transmits the converted application to the client. Distribution method.