# US 2010/0169469 A1 · Request and response decoupling via pluggable transports in a service oriented pipeline architecture for a request response message exchange pattern

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

- Number: US 2010/0169469 A1
- Document ID: US20100169469A1
- Status: Published application
- Kind: A1
- Application number: 12/346,742
- Filed: 2008-12-30
- Published: 2010-07-01
- Earliest claimed: 2008-12-30
- Assignees: eBay Inc.
- Inventors: Sastry K. Malladi; Bhaven Avalani
- Web page: https://patentgrep.com/patent/US20100169469A1

## CPC

- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 65/1066: Session management
- H04L 69/18: Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
- H04L 69/22: Parsing or analysis of headers
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A computer-implemented system and method for decoupling processing of request and response messages supporting different pluggable respective transports in a service-oriented pipeline architecture for a request-response Message Exchange Pattern (MEP) is disclosed. The method in an example embodiment includes receiving a message having coded therein information identifying a desired pluggable transport mechanism respectively for a request and a response; processing the message through a message processing pipeline; dispatching the processed message to a dispatcher; determining if the desired pluggable transport mechanism is available; activating the desired pluggable transport mechanism, if the desired pluggable transport mechanism is available; and transporting the processed message via the desired pluggable transport mechanism.

## Claims

### Claim 1

A method comprising:
receiving a message having coded therein information identifying a desired pluggable transport mechanism for a request and/or a response;
processing the message through a message processing pipeline;
dispatching the processed message to a dispatcher;
determining if the desired pluggable transport mechanism is available;
activating the desired pluggable transport mechanism, if the desired pluggable transport mechanism is available; and
transporting the processed message via the desired pluggable transport mechanism.

### Claim 2 (depends on 1)

The method as claimed in claim 1 including configuring a plurality of pluggable transport mechanisms for use by the dispatcher.

### Claim 3 (depends on 1)

The method as claimed in claim 1 wherein the message processing pipeline and the dispatcher are provided in a client-side environment.

### Claim 4 (depends on 1)

The method as claimed in claim 1 wherein the message processing pipeline and the dispatcher are provided in a server-side environment.

### Claim 5 (depends on 1)

The method as claimed in claim 1 wherein an example desired pluggable transport mechanism uses a Simple Mail Transfer Protocol (SMTP).

### Claim 6 (depends on 1)

The method as claimed in claim 1 wherein an example desired pluggable transport mechanism uses a “Local Transport”

### Claim 7 (depends on 1)

The method as claimed in claim 1 including passing the processed message to a transport factory having a plurality of pluggable transport processors.

### Claim 8 (depends on 7)

The method as claimed in claim 7 wherein the plurality of pluggable transport processors includes at least one pluggable transport processor from the group: Local Transport processor, Hypertext Transport Protocol (HTTP) processor, and Simple Mail Transfer Protocol (SMTP) processor.

### Claim 9 (depends on 8)

The method as claimed in claim 8, wherein the request and response messages can use different transports, in a request-response Message Exchange Pattern(MEP).

### Claim 10

An apparatus comprising:
a message processor to receive a message having coded therein information identifying a desired pluggable transport for a request and/or a response, to process the message through a message processing pipeline, and to dispatch the processed message to a dispatcher; and
a transport factory coupled to the dispatcher, the transport factory including a plurality of pluggable transports, the transport factory to determine if the desired pluggable transport is available, to activate the desired pluggable transport, if the desired pluggable transport is available, and to transport the processed message via the desired pluggable transport.

### Claim 11 (depends on 10)

The apparatus as claimed in claim 10 wherein the message processor and the transport factory are provided in a client-side environment.

### Claim 12 (depends on 10)

The apparatus as claimed in claim 10 wherein the message processor and the transport factory are provided in a server-side environment.

### Claim 13 (depends on 10)

The apparatus as claimed in claim 10wherein an example desired pluggable transport uses a Simple Mail Transfer Protocol (SMTP).

### Claim 14 (depends on 10)

The apparatus as claimed in claim 10 wherein an example desired pluggable transport uses a Local Transport

### Claim 15 (depends on 10)

The apparatus as claimed in claim 10 wherein the plurality of pluggable transports includes at least one pluggable transport from the group: local transport processor, Hypertext Transport Protocol (HTTP) processor, and Simple Mail Transfer Protocol (SMTP) processor.

### Claim 16 (depends on 10)

The apparatus as claimed in claim 10 wherein the request and response messages can use different transports, in a request-response Message Exchange Pattern(MEP).

### Claim 17

An article of manufacture comprising a machine-readable storage medium having machine executable instructions embedded thereon, which when executed by a machine, cause the machine to:
receive a message having coded therein information identifying a desired pluggable transport mechanism for a request and/or a response;
process the message through a message processing pipeline;
dispatch the processed message to a dispatcher;
determine if the desired pluggable transport mechanism is available;
activate the desired pluggable transport mechanism, if the desired pluggable transport mechanism is available; and
transport the processed message via the desired pluggable transport mechanism.

### Claim 18 (depends on 17)

The article of manufacture as claimed in claim 17 wherein the message processing pipeline and the dispatcher are provided in a client-side environment.

### Claim 19 (depends on 17)

The article of manufacture as claimed in claim 17 wherein the message processing pipeline and the dispatcher are provided in a server-side environment.

### Claim 20 (depends on 17)

The article of manufacture as claimed in claim 17 being further configured to pass the processed message to a transport factory having a plurality of pluggable transport processors.

### Claim 21 (depends on 20)

The article of manufacture as claimed in claim 20 wherein the plurality of pluggable transport processors includes at least one pluggable transport processor from the group: local transport processor, Hypertext Transport Protocol (HTTP) processor, and Simple Mail Transfer Protocol (SMTP) processor

### Claim 22 (depends on 20)

The article of manufacture as claimed in claim 20 wherein the request and response messages can use different transports, in a request-response Message Exchange Pattern (MEP).

### Claim 23

A system comprising:
a processor;
a memory coupled to the processor to store information related to messages;
a message processor, operably coupled with the processor and the memory, to receive a message having coded therein information identifying a desired pluggable transport for a request and/or a response, to process the message through a message processing pipeline, and to dispatch the processed message to a dispatcher; and
a transport factory coupled to the dispatcher and operably coupled with the processor and the memory, the transport factory including a plurality of pluggable transports, the transport factory to determine if the desired pluggable transport is available, to activate the desired pluggable transport, if the desired pluggable transport is available, and to transport the processed message via the desired pluggable transport.

### Claim 24 (depends on 23)

The system as claimed in claim 23 wherein the message processor and the transport factory are provided in a client-side environment.

### Claim 25 (depends on 23)

The system as claimed in claim 23 wherein the message processor and the transport factory are provided in a server-side environment.
