# US 2012/0254375 A1 · System and method for connection efficiency

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254375 A1
- Document ID: US20120254375A1
- Status: Published application
- Kind: A1
- Application number: 13/078,950
- Filed: 2011-04-02
- Published: 2012-10-04
- Earliest claimed: 2011-04-02
- Assignees: Recursion Software, Inc.
- Inventors: Robert W. Peterson
- Web page: https://patentgrep.com/patent/US20120254375A1

## CPC

- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- H04L 67/56: Provisioning of proxy services (store-and-forward switching systems in data switching networks H04L12/54)
- H04L 67/566: Grouping or aggregating service requests, e.g. for unified processing
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In a distributed object computing system, a server application may create multiple, uniquely identified, server contexts that each provide one or more services to a service consumer (client). Instead of creating a connection to a client for each server context, a single connection can be used. A service request handler may be configured to handle service requests for each server context. Service requests may be generated in the client with a service context identity. When a service request is received by the server application, the service request handler resolves the service context identity and forwards the service request to the appropriate server context.

## Claims

### Claim 1

A method for providing services from a service provider to a service consumer, the method comprising:
configuring a plurality of server contexts at a device, each server context comprising:
a unique server context identity; and
one or more indexed services;
wherein each server context is configured to provide an indexed service in response to a service request;
configuring a service request handler to handle service requests for the plurality of server contexts;
receiving a service request into the service request handler from the service consumer;
resolving a server context identity of the service request in the service request handler; and
forwarding the service request to the resolved server context;
retrieving an indexed service in the server context; and
generating a service response in the server context, the service response comprising the result of an invocation of the retrieved indexed service.

### Claim 2 (depends on 1)

The method of claim 1 comprising:
creating a connection between the service request handler and the service consumer; and
receiving a plurality of service requests for a plurality of the server contexts on the connection.

### Claim 3 (depends on 2)

The method of claim 2 comprising:
configuring a proxy in the service consumer as a proxy to an indexed service of one of the plurality of server contexts; and
configuring a client context for the proxy that references the server context identity of the respective server context.

### Claim 4 (depends on 3)

The method of claim 3 comprising:
generating a service request in the proxy;
providing the server context identity from the client context into the service request;
sending the service request from the service consumer to the service provider on the connection.

### Claim 5 (depends on 1)

The method of claim 1 comprising generating a server context identity that is independent of a network address of the service provider.

### Claim 6

A method for sharing a connection from a client application on a client device to a server application on a server device comprising a plurality of server contexts, the method comprising:
configuring an endpoint in the client application comprising a connection to the server application;
configuring a plurality of client contexts in the client application, each client context comprising a reference to one of the plurality of server contexts;
generating a service request comprising:
a service request ID;
a namespace ID that identifies one of the plurality of server contexts; and
a service index that identifies a service within the identified server context; and
providing the service request from the client application to the service application on the connection.

### Claim 7 (depends on 6)

The method of claim 6 wherein configuring a client context comprises configuring an identity of the client context as a namespace ID of a server context associated with the client context.

### Claim 8 (depends on 7)

The method of claim 7 comprising configuring a single client context for each server context of the server application.

### Claim 9 (depends on 6)

The method of claim 6 comprising:
receiving the service request in the server application;
passing the service request to a service request handler of the server application;
resolving the namespace ID of the service request;
forwarding the service request to a server context identified by the namespace ID.

### Claim 10 (depends on 6)

The method of claim 6 comprising establishing a physical connection between the client application and the server application on a network address that identifies the server application.

### Claim 11 (depends on 10)

The method of claim 10 wherein the Namespace ID of a server context is independent of the network address.

### Claim 12 (depends on 6)

The method of claim 6 comprising configuring the plurality of server contexts at a server device, each server context comprising:
a unique server context identity;
a services index; and
one or more services indexed by the service index;
wherein each server context is configured to provide a service response comprising the result of an invocation of the retrieved indexed service in response to a service request.

### Claim 13 (depends on 12)

The method of claim 12 comprising configuring a service request handler to handle service requests for the plurality of server contexts.

### Claim 14 (depends on 13)

The method of claim 13 comprising configuring a single server connection between the service request handler and the endpoint of the client application.

### Claim 15

A system comprising:
at least one server device executing a server application configured to create a plurality of server contexts at a network address of the server device, each server context comprising:
a server context identity independent of the network address; and
one or more referenced services;
at least one client device executing a client application configured to:
create a plurality of client contexts as proxies for the one or more referenced services of a respective server context;
generate a service request for the one or more referenced services, the service request comprising a server context identity;
wherein at least one of the client application and the server application is configured to create a network connection between the client application and the server application such that a plurality of service requests to a plurality of the server contexts are able to be provided over the same connection.

### Claim 16 (depends on 15)

The system of claim 15 wherein the server application is configured to create a service request handler that references the plurality of server contexts.

### Claim 17 (depends on 16)

The system of claim 16 wherein the service request handler is configured to:
receive a service request on the connection;
resolve a server context identity from the service request; and
forward the service request to the server context identified by the server context identity in the service request.

### Claim 18 (depends on 16)

The system of claim 16 wherein the service request handler is configured to resolve service requests for each of the plurality of server contexts.

### Claim 19 (depends on 15)

The system of claim 15 wherein each client context stores a server context identity of the respective server context.

### Claim 20 (depends on 15)

The system of claim 15 wherein each server context comprises on object request broker that references the services available for the respective server context.
