Method and system for data processing

• US 8,352,619 B2
• Filed: 03/09/2012
• Issued: 01/08/2013
• Est. Priority Date: 11/28/2008
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Guo, Ming Liang, Wang, Deyu, Wu, Wei Lei
• Primary Examiner(s): Chan, Wing
• Assistant Examiner(s): WOO, ANDREW M
• Application Number:
  US13/416,948
• Publication Number:
  US 20120173737A1
• Time in Patent Office: 305 Days
• Field of Search: 709/227, 709/228
• US Class Current: 709/227
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding

Abstract

A computer-implemented method for protecting data being transferred during a session with an application is presented. In response to receiving a session request that includes an application identifier for an application, a data processing node establishes a session with the application and assigns a session identifier for that session. A session response, which includes the session identifier, to the session request is sent. In response to receiving a first request that includes the session identifier, a first pipe in the session is established. This first pipe enables data related to the first request to be isolated according to an assigned first pipe identifier for the first pipe. A first response to the first request is sent, wherein the first response comprises the session identifier and the first pipe identifier.

Claims

1. A computer-implemented method comprising:

establishing, by a first data processing node, a session between a first application in the first data processing node and a second application in a second data processing node, wherein said session is established in response to a session request that comprises an application identifier for the first application;

assigning a session identifier for said session;

sending, from said first data processing node, a session response to said session request, wherein said session response comprises said session identifier;

establishing, by said first data processing node, a first pipe in said session to perform data isolation on processing related to a first request, wherein said first pipe is a communication path between a first process and a second process, wherein the first process is a first thread in the first application and the second process is a first thread in the second application, wherein said first pipe is isolated from other pipes in the session, and wherein said first pipe is established in response to said first data processing node receiving said first request that comprises said session identifier;

assigning a first pipe identifier for said first pipe;

sending, by said first data processing node, a first response to said first request, wherein said first response comprises said session identifier and said first pipe identifier;

establishing, by said first data processing node, a second pipe in said session to perform data isolation on processing related to a second request, wherein said second pipe is a communication path between a second thread in the first application and a second thread in the second application, and wherein the first pipe and the second pipe operate concurrently during the session;

assigning a second pipe identifier for said second pipe, wherein said second pipe is established in response to said first data processing node receiving said second request that comprises said session identifier but does not comprise said first pipe identifier;

using the session identifier to identify the first pipe and the second pipe as being sub-sessions of the session; and

sending, by said first data processing node, a second response to said second request, wherein said second response comprises said session identifier and said second pipe identifier.

2. The computer-implemented method of claim 1, wherein said session request is received and said session response is sent on a first transport layer connection, wherein said first request is received and said first response is sent on a second transport layer connection, wherein said session request and said first request are received concurrently at the first data processing node, and wherein said second request is received and said second response is sent on a third transport layer connection.

3. The computer-implemented method of claim 1, wherein said session response further comprises said application identifier, wherein said first request further comprises an identifier of the first thread in the first application, wherein said second request further comprises an identifier of the second thread in the first application, wherein said first response further comprises an identifier of said first thread in the first application, and wherein said second response further comprises an identifier of said second thread in the first application.

4. The computer-implemented method of claim 1, wherein said session request and said first request are received on a first transport layer connection, wherein said session response and said first response are sent on said first transport layer connection, and wherein said second request is received and said second response is sent on a second transport layer connection.

5. The computer-implemented method of claim 1, wherein said first data processing node assigns session storage space for said session, wherein said first data processing node assigns first pipe storage space for said first pipe, and wherein said first data processing node assigns second pipe storage space for said second pipe.

6. The computer-implemented method of claim 5, wherein said first data processing node stores data shared in said session in said session storage space, wherein said first data processing node stores a first set of data, which has been selected for isolation, in said first pipe storage space, and wherein said first data processing node stores a second set of data, which has also been selected for isolation, in said second pipe storage space.

7. The computer-implemented method of claim 5, further comprising:

sending, by said first data processing node, a third response to a third request, wherein said third response is sent in response to said first data processing node receiving said third request that comprises said session identifier and said first pipe identifier, wherein said third response comprises said session identifier and said first pipe identifier, and wherein said third request, said third response, said first request and said first response share said first pipe storage space.

8. The computer-implemented method of claim 1, further comprising:

sending, by said first data processing node, a third response to a third request, wherein said third response comprises said session identifier and said first pipe identifier, and wherein said third response is sent in response to said first data processing node receiving said third request that comprises said session identifier and said first pipe identifier.

9. The computer-implemented method of claim 1, wherein data in the session is shared through said session identifier, wherein data of said first pipe is accessed through said session identifier and said first pipe identifier, and wherein data of said second pipe is accessed through said session identifier and said second pipe identifier.

10. The computer-implemented method of claim 1, further comprising:

active releasing said first pipe, wherein said active releasing allows said first pipe to be used by other data requests.

11. The computer-implemented method of claim 1, further comprising:

timeout releasing said first pipe, wherein said timeout releasing allows other data requests to use said first pipe after a timeout period expires.

12. The computer-implemented method of claim 1, wherein said first data processing node establishes said first pipe in response to said first request based on said application identifier.

13. The computer-implemented method of claim 1, wherein said first request comprises a request to establish a pipe.

14. The computer-implemented method of claim 1, further comprising:

said first data processing node determining a maximum number of pipes that are permitted to be established in said session.