JP2013218670A - Computer mounting method, computer system and computer readable recording medium - Google Patents

Abstract

A computer-implemented method for processing a request to connect to a server from an application on a client device.
A method receives a request to connect to a server from an application on a client device, determines a matching service interface, determines an access indicator for the matching service interface, and connects to a server Responsive to the request, including sending a matching service interface access indicator to an application on the client device.
[Selection] Figure 4

Description

  The present application relates to a computer-implemented method, a computer system, and a computer-readable recording medium.

  In traditional client-server computing, widely distributed applications can partition tasks, workloads, and / or application processes between at least two devices. For example, a distributed application can be partitioned between a service requester known as a client and a service provider known as a server. A client can request services provided by a server over a network. For example, a client can request a computing service or an email service provided by a server over a network such as the Internet.

  During a distributed application upgrade in a client-server computing environment, it may be necessary to configure application code or client software on the client device and / or application code or server software on the server device. However, configuring upgraded client software on the client device can result in many problems. For example, a client device user may ignore notifications from a server that requires client software configuration and continue to use client software that has not been upgraded. In addition, client device users may attempt to use the upgraded client software without configuring it. In addition, even if the user of the client device attempts to configure the upgraded client software, an error will occur during configuration so that the upgraded client software points to non-existing server software May be.

  The details of one or more implementations are set forth in the accompanying exemplary drawings and the exemplary description below. Other features will be apparent from the description and drawings, and from the claims.

  The problem is solved by the means described in the claims.

FIG. 2 is an exemplary system architecture diagram according to one embodiment. FIG. 3 is an exemplary schematic diagram according to one embodiment. FIG. 3 is an exemplary schematic diagram according to one embodiment. FIG. 3 is an exemplary schematic diagram according to one embodiment. FIG. 3 is an exemplary schematic diagram according to one embodiment. FIG. 2 illustrates an exemplary service interface management system according to one embodiment. FIG. 3 illustrates an exemplary method according to one embodiment. FIG. 6 illustrates another exemplary method according to one embodiment. FIG. 3 illustrates an exemplary registration service according to one embodiment. FIG. 6 illustrates an exemplary computer system and / or computer network system for implementing the computer systems and methods shown in FIGS. 1-5, according to one embodiment.

  Hereinafter, a detailed description of embodiments will be provided with reference to the drawings. It should be understood that various modifications can be made to these embodiments. In particular, one or more elements of one or more embodiments can be separated from each other and used in combination and / or in other embodiments to form new embodiments. Can do.

  FIG. 1 illustrates an exemplary system architecture diagram 100 for communication between a server 101 and a client device 102 over a network 103, according to one embodiment. Server 101 may be a computing device such as a computer. Client device 102 may be a smartphone, tablet computer, personal digital assistant (PDA), desktop computer, laptop, and the like.

  According to one embodiment, the server 101 can host or provide one or more services, such as 104-106. A service can be a computer process, software, or application that performs a specific function. A service may have one or more versions. For each version of a service, a service interface, also called a contract, can be provided on the server 101 to allow applications to access this version of the service. For example, in FIG. 1, service interfaces 104a-n are provided for available versions of service 104. A service interface can also be provided for the services 105 and 106. A service interface that allows application access to a version of the service can be accessed via an access indicator. An example of an access indicator would be a uniform resource locator (URL) or other pointer to the access indicator.

  The server 101 may be one of a plurality of versions. If multiple versions are provided for a single server, such as server 101, a newer version of the server may provide more service interfaces than an older version of the server. In addition, if multiple instances of a particular version of the server are implemented, for example if each instance of a particular version of the server is implemented in a different business, it corresponds to a particular version of the service on the server instance Each service interface is addressable via a different access indicator. For example, an instance of server X is implemented by company A, and another instance of server X is implemented by company B. To access the service interface on company A's server X, the client application can use an access indicator such as a URL (eg, http (s): //companya.com/svc). To access the service interface for the same version of the same service on Company B's server X, the client application uses a different access indicator, such as a different URL (for example, http (s): //companyb.com/svc) can do.

  Client device 102 may include a client application 107. Client application 107 may include code and may be preinstalled on client device 102 or downloaded to client device 102. The client application 107 can use one or more service interfaces on the server 101. For example, the client application 107 can use only the service interface 104a and can therefore be considered a static client application. Another approach involves the client application 107 being enabled to use selected ones of the service interfaces 104a-n, such as the service interface 104a, service interface 104b, and service interface 104c, and thus Think of it as a multi-static client application. In static and multi-static client applications, the service interface can be addressed by an access indicator encoded in the client application 107 code. For example, a client application can access a specific version of a service interface using an access indicator such as a URL (eg, http (s): //companya.com/svc).

  Pseudocode example for a multi-static client application:

  Advantageously, client applications can switch to a newer service interface as soon as possible, but avoid disruptive switching during the application runtime. During the application runtime, the client application may detect a newer version of the service interface, but the newer service interface will be used at the next launch of the application.

  In yet another approach, the client application 107 is enabled to use all service interfaces provided by the server 101, such as service interfaces 104a-n, and is therefore considered a dynamic client application. One or more specific service interfaces that can be used by the client application 107 are considered acceptable service interfaces. For example, the dynamic client application may be a browser type / general client type application.

  The dynamic application can include an access identifier for the service interface management system and can pass input parameters to the service interface management system in a request to the service interface management system. The input parameter may be an application identifier representing the purpose of the application, such as an employee list or an opportunity list, rather than an acceptable service interface. The service interface management system can collate the service interfaces belonging to the application identifier and determine the best matching service interface from these service interfaces.

  Pseudocode example for a dynamic client application:

  In addition, the dynamic application can include a latest version link that allows the application to upgrade to that version as soon as a newer version of the service interface becomes available on the server. The response payload of a request addressing a specific service interface must include an access identifier to the latest (newest) version so that a general client can switch to the latest (newest) version of this service interface. I must.

  Another example of pseudocode for a dynamic client application:

  If multiple versions of an application are provided for a single application, a newer version of the application may be able to use more service interfaces than an older version of the application. In other words, a newer version of an application may have more acceptable service interfaces than an older version of the application. According to one embodiment, the next version of the application may use one more service interface than the immediately previous version of the application. In addition, specific versions of applications can be installed and used by many users. That is, there may be many instances of a particular version of the application.

  While either server 101 and client application 107 on client device 102 are upgraded, a switch from an older version of the server and / or client application to a newer version of the server and / or client application is performed. The However, the client application 107 may not include the correct access indicator needed to access the service interface on the server 101 after the upgrade is performed. For example, an upgraded client application downloaded by Company A may need to be configured to access a new service interface on Company A's server.

(Example)
FIG. 2a shows that server S1 provides a service interface C1 that lists all employees with first name, last name, and phone number. The employee directory application A1 displays all employees with first name, last name, and phone number. The application A1 can use the service interface C1. Application A1 can be an application provided in an application store and can be downloaded by a separate entity.

  Two companies, company A, example.org, company B, and smallexample.com, implement separate instances of server S1 and application A1, as described above and as shown in FIG. 2b. To ensure that Company A and Company B each display the correct employee directory, the access indicator must be properly configured. For example, both company A and company B can download application A1 from the application store. Company A addresses and accesses Company A's service interface C1 using an access indicator, eg, URL, https://example.org/u. Company B addresses and accesses Company B's service interface C1 using a different access indicator, eg, URL, https://smallexample.com/v.

  Thus, employees using Company A's application A1 must enter an access indicator, for example, URL, https://example.org/u, and employees using Company B's application A1 You have to enter an indicator, for example URL, https://smallexample.com/v.

  In FIG. 2c, when the employee directory application A1 is expanded or upgraded, the next version of the application, for example application A2, has an additional function, for example the ability to display employee photos in addition to other employee data. There is a case. Application A2 can accept both service interface C1 and service interface C2, but application A1 still accepts only service interface C1. Furthermore, both company A and company B may still use server S1.

  When the application A2 is distributed through the application store, the application A2 is shown as a new version of the application A1 in the update notice for the application A1 user in both the company A and the company B. For example, an email notification may be sent to employees of company A and company B that use application A1 indicating that there is a new version of application A1.

  Thus, some employees may update application A1 to application A2, but the remaining employees may not update application A1 to application A2 and still use application A1 instead. Since application A1 accepts service interface C1 and server S1 provides service interface C1, application A1 will still function. As shown in FIG. 2c, application A2 can still accept service interface C1 in addition to service interface C2, and server A1 provides service interface C1, so application A2 will work.

  FIG. 2d shows a scenario in which company A switches to server version S2 that provides service interface C1 and service interface C2. When server S2 is upgraded, the next server version S2 can provide a service interface C2 that lists all employees with first name, last name, phone number, and photo in addition to service interface C1. Since the service interface C1 is a stable service interface and cannot be changed or deleted, the service interface C1 is still provided. Application A1 will still accept the service interface C1 provided by server S2. Application A2 will receive a service interface C2 now provided by server S2 and a service interface C1 still provided by server S2.

  However, the access indicators in application A1 and application A2 must point to the appropriate service interface in order to access the correct version and service provided by the server. Accordingly, in one embodiment, a service interface management system is provided for configuring an upgraded client application on a client device.

  FIG. 3 shows an exemplary service interface management system 300. According to one embodiment, a service interface management system 300 is provided to reduce configuration effort when upgrading an application or server. The service interface management system 300 includes a request reception module 310, a match determination module 320, and an access indicator module 330. The match determination module 320 may further comprise an acceptable service interface module 340 and a best match service interface module 350.

  The service interface management system 300 can be realized as hardware, a software platform, or a cloud. For example, the service interface management system 300 may include an example of cloud computing. Cloud computing provides computing, software, data access, storage resources, etc. without requiring the cloud user or client device to know the location and other details of the computing infrastructure. Thus, a cloud may include delivery of computing as a service when shared resources, software, and information are provided as services to computers and other devices over a network. Access to cloud-based applications can be via a client device, such as a web browser or portal, a lightweight desktop or mobile application.

  On the client application side, instead of encoding the service interface access indicator into the client application, the client application can include the service interface management system 300 access indicator. For example, Company A would encode an access indicator for Company A's service interface management system in the client application, and Company B would encode a different access indicator for Company B's service interface management system in the client application. Will do. Thus, when a request is made from a client application, the request is automatically sent to the service interface management system 300 using an access indicator such as a URL of the service interface management system 300. The service interface management system 300 can provide an access indicator to the client device in response to a request from the client device. The service interface management system 300 can provide an access indicator for each type of application in the business and for all versions of a single application in the business.

  The request receiving module 310 can receive a request from a client application residing on the client device indicated by the access indicator. The request may include input parameters from the client application (which may be encoded with the input parameters). The input parameter may represent one or more service interfaces that are acceptable to the client application.

  The match determination module 320 can determine a match service interface. As discussed above, the match determination module 320 may further comprise an acceptable service interface module 340 and a best match service interface module 350. To determine the matching service interface, the acceptable service interface module 340 can determine the value of the input parameter from the request received by the request reception module 310 from the client application. The input parameter may represent one or more service interfaces that are acceptable to the client application. For example, referring to FIG. 1, the client application 107 can access the service 104 only through the service interfaces 104a and 104b. Thus, service interfaces 104a and 104b are acceptable service interfaces.

  The acceptable service interface module 340 can also retrieve the service interface provided by the server from the data storage device. The data storage device may be coupled to a server or coupled to the service interface management system 300. For example, referring to FIG. 1, the service interfaces provided by the server 101 can be service interfaces 104a-n.

  The acceptable service interface module 340 can then determine whether any of the one or more acceptable service interfaces matches any of the service interfaces provided by the server. If more than one matching service interface is determined by the acceptable service interface module 340, the best matching service interface module 350 can determine the best matching service interface from the matching service interfaces. The best matching service interface may be the newest version of the matching service interface based on a predetermined order of application versions. Alternatively, the best matching service interface may be the most relevant matching service interface. In addition, if no match is determined, the service interface management system 300 sends an error message to the client application on the client device indicating that the application will not work.

  Once the matching service interface is determined, the access indicator module 330 can determine an access indicator for the matching service interface. The access indicator of the matching service interface can be a uniform resource locator (URL) of the matching service interface. For example, the URL for a service interface can be determined from a look-up table that stores service interfaces and their corresponding access indicators (eg, URLs). The access indicator module 330 can then send a matching service interface access indicator, eg, a URL, to the client application on the client device. The client device can use the access indicator to connect to the server via the appropriate service interface.

In summary, a service interface management system for processing a request to connect to a server from an application on a client device can be provided.
A request receiving module configured to receive a request to connect to a server from an application on a client device;
A match determination module configured to determine a match service interface;
An access indicator module configured to determine a matching service interface access indicator and send the matching service interface access indicator to an application on the client device in response to a request to connect to the server. The match determination module
Determining from the request input parameters representing one or more service interfaces acceptable to the application; and
An acceptable service interface module configured to determine whether any of the one or more acceptable service interfaces matches a service interface provided by the server;
A best matching service interface module configured to determine the best matching service interface when more than one matching service interface is determined.

  Advantageously, the application only needs to know one access indicator, the URL of the service interface management system 300. By accessing this access indicator, no other configuration information is required. This is because the service interface management system 300 provides the configuration or URL to the client application. The service interface access indicator is a service interface to which the client application should connect so that the client application can connect to the server. Even when the client application itself is upgraded, the URL of the service interface management system 300 may be hard-coded in the client application code. Thus, the upgraded client application will still point to the service interface management system 300. Furthermore, the client application will automatically switch to the best version with respect to the version of the service interface provided by the server.

  The computer system described above may be operable to perform the methods described below with respect to FIGS.

  FIG. 4 illustrates an exemplary method 400 according to one embodiment. The method 400 illustrates the steps associated with responding to a request to connect to a server from an application residing on a client device, according to one embodiment.

  In step 410, the service interface management system receives a request to connect to the server from an application on the client device. The request may be directly from an application on the client device or may be routed through another service, such as a registration service. In other words, in the service interface management system, receiving a request to connect to the server from an application on the client device may further include determining an access identifier of the service interface management system from the registration service.

  In step 420, the service interface management system determines a matching service interface. This step is described in more detail below with respect to FIG.

  At step 430, the service interface management system determines an access indicator for the matching service interface. The access indicator of the matching service interface can be a uniform resource locator (URL) of the matching service interface.

  In step 440, the service interface management system sends a matching service interface access indicator to the client application on the client device in response to the request to connect to the server.

  FIG. 5 illustrates an exemplary method 500 describing step 420 of the method 400 of FIG. 4, according to one embodiment. Method 500 illustrates the steps associated with determining a matching service interface, according to one embodiment.

  In step 510, the service interface management system determines input parameters from the request. The input parameter represents one or more service interfaces that are acceptable to the application.

  At step 520, the service interface management system determines whether any of the one or more acceptable service interfaces matches any service interface provided by the server. That is, one or more matching service interfaces are determined. If more than one matching service interface is determined at step 520, the method proceeds to step 530. If only one matching service interface is determined, the method 500 ends and returns to step 430 of the method 400.

  In step 530, the service interface management system determines the best matching service interface from the two or more matching service interfaces. The best matching service interface may be the newest version of the matching service interface based on a predetermined order of application versions. Alternatively, the best matching service interface may be the most relevant matching service interface.

  After determining the best matching service interface, method 500 ends and returns to step 430 of method 400. Here, the best matching service interface is the matching service interface.

In view of the foregoing method, a computer-readable recording medium can be provided. The computer readable recording medium may be operable to process a request from a client device to connect to a server. The computer-readable recording medium may comprise computer-executable instructions that, when executed,
Receiving a request to connect to a server from an application on a client device;
Determining a matching service interface;
Determining an access indicator for a matching service interface;
Responsive to a request to connect to the server, transmitting a matching service interface access indicator to an application on the client device.

Furthermore, a client side application can be provided. A client-side application may be on the client device to connect to the server, and the client application
Send a request to connect to the server to the service interface management system,
In response to a request to connect to the server, a matching service interface access indicator is received from the service interface management system;
It is configured to connect to the server based on the received access indicator.

Furthermore, a server can be provided. The server can handle requests to connect to the service interface from applications on the client device,
A plurality of service interfaces are provided that allow access to services on the computer, each service interface being addressable using an access identifier by an application on the client device.

Cloud-based Registration Service FIG. 6 shows a registration service 600 used with a service interface management system as described above in FIG. According to one embodiment, registration service 600 may include hardware, software, or cloud-based services. Registration service 600 allows a company to register a company-specific access indicator of the company-specific service interface management system. For example, company A can register the access indicator of company A's service interface management system 300 in registration service 600. Similarly, company B can register the access indicator of company B's service interface management system 300 with the same registration service 600. After registration, both company A and company B client applications 107 can be hard-coded with the access indicator or URL of registration service 600.

  Registration service 600 may provide an appropriate access indicator to the requesting company. For example, if company A requests an access indicator from registration service 600, company A will receive its own service interface management system 300 access indicator. When company B requests an access indicator from registration service 600, company B will receive its own service interface management system 300 access indicator.

  Thus, on the client side, the company need only maintain the access indicator of the registration service 600 in the client application 107, rather than maintaining its own service interface management system 300 access indicator in the client application 107. Advantageously, the access indicator of the registration service 600 is the same for all client applications 107 and can be hard coded in the client application 107.

  Further, in response to registration with the registration service 600, the registration service 600 can provide Company A with an activation code that is easy to type and store. Registration service 600 may also provide company B with an activation code that is different from the activation code provided to company A in response to company B registering with registration service 600. When Company A and Company B employees can download their client application 107, they typically enter configuration information, but simply enter an activation code for each company into client application 107. .

  When the client application 107 is activated by an employee of company A, a request to read an access indicator, ie URL, of the service interface management system 300 of company A is sent to the registration service 600. Similarly, when the client application 107 is launched by an employee of company B, a request to read an access indicator or URL of the service interface management system 300 of company B is sent to the registration service 600. Accordingly, the registration service 600 returns an appropriate access indicator to the requesting company in exchange for the activation code. Alternatively, if a client application is tied to a specific device with a unique identifier, such as a mobile device with an IMEI number, a company can register multiple devices with unique identifiers with the registration service 600. . For example, an application programming interface (API) can read the device's IMEI number and provide the IMEI number to the registration service 600. The registration service 600 can register the IMEI number of each device belonging to a group having a specific access identifier (such as a URL of a company service interface management system 300). Therefore, all devices belonging to a certain group or company can be registered in the registration service 600. When the client application is launched on the registered device, the IMEI number is automatically provided to the registration service 600, and the registration service can respond with an access identifier associated with the IMEI number. Advantageously, the client application can then request the access identifier of the service interface management system 300 from the registration service 600 using a unique identifier such as an IMEI number instead of the activation code.

  FIG. 7 illustrates an exemplary system for implementing the method, including a general purpose computing device in the form of a conventional computing environment 920 (eg, a server). This conventional computing environment includes a processing unit 922, a system memory 924, and a system bus 926. The system bus couples various system components including the system memory 924 to the processing unit 922. The processing unit 922 can perform arithmetic, logic, and / or control operations by accessing the system memory 924. The system memory 924 can store information and / or instructions used with the processing unit 922. System memory 924 may include volatile and non-volatile memory, such as random access memory (RAM) 928 and read only memory (ROM) 930. The ROM 930 may store a basic input / output system (BIOS) including basic routines that help to transfer information between elements in the server 920, such as during startup. The system bus 926 can be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.

  Server 920 may further include a hard disk drive 932 for reading from and writing to a hard disk (not shown) and an external disk drive 934 for reading from and writing to removable disk 936. The removable disk can be a magnetic disk for a magnetic disk drive or an optical disk such as a CD ROM for an optical disk drive. The hard disk drive 932 and external disk drive 934 are connected to the system bus 926 by a hard disk drive interface 938 and an external disk drive interface 940, respectively. The drives and their associated computer readable recording media provide the server 920 with non-volatile storage of computer readable instructions, data structures, program modules, and other data. The data structure may include relevant data for performing the method as described above. Related data can be organized in a database, such as a relational database management system or an object-oriented database management system.

  The exemplary environment described herein employs a hard disk (not shown) and an external disk 936, but is accessible by a computer, such as a magnetic cassette, flash memory card, digital video disk, random access memory, read-only memory, etc. Those skilled in the art will appreciate that other types of computer readable recording media that can store various data may be used in the exemplary operating environment.

  The hard disk, external disk 936, ROM 930, or RAM 928 includes several items, including an operating system (not shown), one or more application programs 944, other program modules (not shown), and program data 946. Program modules can be stored. The application program may include at least a part of the functions shown in FIGS.

  A user may enter commands and information into the server 920 through input devices such as a keyboard 948 and a mouse 950 as discussed below. Other input devices (not shown) may include a microphone (or other sensor), joystick, game pad, scanner, and the like. These and other input devices can be connected to the processing unit 922 via a serial port interface 952 coupled to the system bus 926, or a parallel port interface 954, game port, or universal serial bus (USB), etc. Can be connected by other interfaces. In addition, information can be printed using printer 956. The printer 956 and other parallel input / output devices can be connected to the processing unit 922 via a parallel port interface 954. A monitor 958 or other type of display device is also connected to the system bus 926 via an interface, such as a video input / output 960. In addition to the monitor, the computing environment 920 may include other peripheral output devices (not shown), such as speakers and other audible outputs.

  The computing environment 920 can communicate with other electronic devices such as computers, telephones (wired or wireless), personal digital assistants, televisions, and the like. To communicate, the computer environment 920 can operate in a networked environment using connections to one or more electronic devices. FIG. 7 illustrates a computer environment networked with a remote computer 962 or mobile device 102. The remote computer 962 can be another computing environment, such as a mobile device such as a smartphone or tablet, and can include many of the elements described above with respect to the computing environment 920. The logical connections shown in FIG. 7 include a local area network (LAN) 964 and a wide area network (WAN) 966. Such networking environments are common in offices, enterprise-wide computer networks, intranets, and the Internet, and can be particularly encrypted.

  When used in a LAN networking environment, the computing environment 920 may be connected to the LAN 964 via a network I / O 968. When used in a WAN networking environment, the computing environment 920 may comprise a modem 970 or other means for establishing communications over the WAN 966. Modem 970 is internal or external to computing environment 920 and is connected to system bus 926 via serial port interface 952. In a networked environment, program modules illustrated relative to computing environment 920 or portions thereof may be stored on a remote memory storage device that is on or accessible from remote computer 962. Further, other data related to the method may also be on or accessible via the remote computer 962. It will be appreciated that the network connections shown are exemplary and other means of establishing a connection link between the electronic devices may be used.

  The foregoing computing system is only one example of the type of computing system that can be used with the method described above.

101 servers
102 client devices
103 network
104, 105, 106 services
104a-n Service interface
107 client applications

Claims (15)

A computer-implemented method for processing a request to connect to a server from an application on a client device,
In the service interface management system, receiving the request to connect to the server from the application on the client device;
Determining a matching service interface in the service interface management system;
Determining an access indicator of the matching service interface in the service interface management system;
Transmitting the access indicator of the matched service interface to the application on the client device in response to the request to connect to the server from the service interface management system. The step of determining a matching service interface is
Determining from the request input parameters representing one or more service interfaces acceptable to the application;
The method of claim 1, comprising: determining whether any of the one or more acceptable service interfaces matches a service interface provided by the server. If two or more matching service interfaces are determined, determine the best matching service interface,
3. The method of claim 2, wherein the best matching service interface is the newest version of the matching service interface.   The method according to any one of claims 1 to 3, wherein the access indicator of a matching service interface is a uniform resource locator (URL) of the service interface.   In the service interface management system, the step of receiving the request to connect to the server from the application on the client device further comprises determining an access identifier of the service interface management system from a registered service. Item 5. The method according to any one of Items 1 to 4. A service interface management system for processing a request to connect to a server from an application on a client device,
A request receiving module configured to receive the request to connect to the server from the application on the client device;
A match determination module configured to determine a match service interface;
An access indicator configured to determine an access indicator for the matching service interface and send the access indicator for the matching service interface to the application on the client device in response to the request to connect to the server. Service interface management system comprising modules. The match determination module further comprises:
An acceptable service interface module, the acceptable service interface module comprising:
Determining from the request input parameters representing one or more service interfaces acceptable to the application;
The service interface management system of claim 6, configured to determine whether any of the one or more acceptable service interfaces matches a service interface provided by the server. The match determination module further comprises a best match service interface module configured to determine a best match service interface when two or more match service interfaces are determined;
8. The service interface management system of claim 7, wherein the best matching service interface is the newest version of the matching service interface.   9. The service interface management system according to any one of claims 6 to 8, wherein the access indicator of a matching service interface is a uniform resource locator (URL) of the service interface. A computer-readable recording medium for processing a request to connect to a server from an application on a client device, comprising computer-executable instructions, and when the computer-executable instructions are executed,
In the service interface management system, receiving the request to connect to the server from the application on the client device;
Determining a matching service interface;
Determining an access indicator for the matching service interface;
Transmitting the access indicator of the matching service interface to the application on the client device in response to the request to connect to the server. The step of determining a matching service interface is
Determining from the request input parameters representing one or more service interfaces acceptable to the application;
11. The computer readable recording medium of claim 10, comprising determining whether any of the one or more acceptable service interfaces matches a service interface provided by the server. If two or more matching service interfaces are determined, determine the best matching service interface,
12. The computer readable recording medium of claim 11, wherein the best matching service interface is the newest version of the matching service interface.   The computer-readable recording medium according to any one of claims 10 to 12, wherein the access indicator of a matching service interface is a uniform resource locator (URL) of the service interface. A client-side application on the client device to connect to the server,
Sending a request to connect to the server to the service interface management system;
In response to the request to connect to the server, an access indicator for a matching service interface is received from the service interface management system;
A client-side application configured to connect to the server based on the received access indicator. A server that handles requests to connect to a service interface from an application on a client device,
A server comprising a plurality of service interfaces allowing access to services on a computer, each service interface being addressable using an access identifier by the application on the client device.