Handling multi-pipe connections

Patent metadata

Field	Value
Publication number	US-9948724-B2
Application number	US-201514849739-A
Country	US
Kind code	B2
Filing date	Sep 10, 2015
Priority date	Sep 10, 2015
Publication date	Apr 17, 2018
Grant date	Apr 17, 2018

Abstract

Methods, systems, and computer program products for handling multi-pipe connections is provided. A primary pipe request for a connection between a client and a server is received. The connection includes a plurality of pipes between the client and the server. The primary pipe request includes a number corresponding to the amount of pipes required for the connection. A first response acknowledging the receipt of the primary pipe request is transmitted. The first response includes a token. A plurality of subsequent pipe requests are received for the connection between the client and the server. Each subsequent pipe request includes the token. A subsequent response to each subsequent pipe request is transmitted. A count of the number of pipe requests received is maintained. The established pipes are released after a period of time has elapsed when the number of pipe requests received doesn't reach the number of pipes required for the connection.

First claim

What is claimed is:

1. A computer program product, the computer program product comprising:
a computer readable storage medium, wherein the computer readable storage medium is not a transitory signal per se, and program instructions stored on the computer readable storage medium, the program instructions comprising:
program instructions to receive a primary pipe request for a connection between a client and a server, wherein the connection comprises a plurality of pipes between the client and the server, and wherein the primary pipe request comprises a number corresponding to the amount of pipes required for the connection;
program instructions to generate a token, wherein the token comprises a plurality of unique characters used by a primary task to maintain a count of a number of pipe requests received;
program instructions to transmit a first response acknowledging receipt of the primary pipe request for the connection, wherein the first response comprises the token for the connection, and wherein the first response indicates that a first pipe has been established;
program instructions to receive a plurality of subsequent pipe requests for the connection between the client and the server, wherein each subsequent pipe request includes the token for the connection;
program instructions to transmit a subsequent response to each subsequent pipe request, wherein the subsequent response indicates that a respective pipe has been established;
program instructions to maintain the count of the number of pipe requests received; and
program instructions to release the established pipes after a period of time has elapsed, wherein the count of the number of pipe requests received does not reach the number for the pipes required for the connection.

2. The computer program product of claim 1 , further comprising:
program instructions to start the primary task, wherein the primary task stores the number of pipes required for the connection.

3. The computer program product of claim 2 , further comprising:
program instructions to suspend the primary task in response to receiving a first subsequent pipe request;
program instructions to resume the primary task in response to receiving a new pipe request; and
program instructions to terminate the primary task in response to the count of the number of pipe requests received equalling the number of pipes required for the connection.

4. The computer program product of claim 2 , further comprising:
program instructions to start a secondary task, wherein the secondary task corresponds to each subsequently received pipe request.

5. The computer program product of claim 4 , further comprising:
program instructions to establish a pipe between the client and the server, wherein the pipe corresponds to the respective pipe request; and
program instructions to terminate the secondary task in response to establishing the pipe for the respective pipe request.

6. The computer program product of claim 2 , wherein the primary task is further operated to set a time limit on a period for waiting to receive the next pipe request prior to releasing the established pipes if the count of the number of pipe requests received does not reach the number for the pipes required for the connection.

7. A computer system, the computer system comprising:
one or more computer processors;
one or more computer readable storage media, wherein the computer readable storage media is not a transitory signal per se;
program instructions stored on the computer readable storage media for execution by at least one of the one or more processors, the program instructions comprising:
program instructions to receive a primary pipe request for a connection between a client and a server, wherein the connection comprises a plurality of pipes between the client and the server, and wherein the primary pipe request comprises a number corresponding to the amount of pipes required for the connection;
program instructions to generate a token, wherein the token comprises a plurality of unique characters used by a primary task to maintain a count of a number of pipe requests received;
program instructions to transmit a first response acknowledging receipt of the primary pipe request for the connection, wherein the first response comprises the token for the connection, and wherein the first response indicates that a first pipe has been established;
program instructions to receive a plurality of subsequent pipe requests for the connection between the client and the server, wherein each subsequent pipe request includes the token for the connection;
program instructions to transmit a subsequent response to each subsequent pipe request, wherein the subsequent response indicates that a respective pipe has been established;
program instructions to maintain the count of the number of pipe requests received; and
program instructions to release the established pipes after a period of time has elapsed, wherein the count of the number of pipe requests received does not reach the number for the pipes required for the connection.

8. The computer system of claim 7 , further comprising:
program instructions to start the primary task, wherein the primary task stores the number of pipes required for the connection.

9. The computer system of claim 8 , further comprising:
program instructions to suspend the primary task in response to receiving a first subsequent pipe request;
program instructions to resume the primary task in response to receiving a new pipe request; and
program instructions to terminate the primary task in response to the count of the number of pipe requests received equalling the number of pipes required for the connection.

10. The computer system of claim 8 , further comprising:
program instructions to start a secondary task, wherein the secondary task corresponds to each subsequently received pipe request, and wherein the primary task is further operated to set a time limit on a period for waiting to receive the next pipe request prior to releasing the established pipes if the count of the number of pipe requests received does not reach the number for the pipes required for the connection.

11. The computer system of claim 10 , further comprising:
program instructions to establish a pipe between the client and the server, wherein the pipe corresponds to the respective pipe request; and

program instructions to terminate the secondary task in response to establishing the pipe for the respective pipe request.

Assignees

• IBM

Inventors

• Brooks Michael D
• Hollingshead Alan
• Horn Julian C
• Wakelin Philip I

Classifications

• H04L67/143

  Termination or inactivation of sessions, e.g. event-controlled end of session · CPC title

• H04L67/141 Primary

  Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70) · CPC title

• H04L69/14

  Multichannel or multilink protocols · CPC title

• H04L1/1621

  Group acknowledgement, i.e. the acknowledgement message defining a range of identifiers, e.g. of sequence numbers · CPC title

• H04L67/42

  Electricity · mapped topic