Protocol Agnostic Request Response Pattern

• US 20100228873A1
• Filed: 05/19/2010
• Published: 09/09/2010
• Est. Priority Date: 03/27/2001
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Firth, Richard L., Nielsen, Henrik Frystyk, Olson, Lance E., Sanders, Henry L.
• Application Number:
  US12/783,428
• Publication Number:
  US 20100228873A1
• Time in Patent Office: Days
• US Class Current: 709/230
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: H04L 69/03 Protocol definition or specification protocol conformance testing H04L1/244
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A system and method for facilitating communications over a protocol is provided. The system includes a class factory that holds identifiers associated with determining which, if any, registered protocol object creator should be employed to create a protocol object. The protocol object implements an abstract network protocol base class. The protocol object is employed to abstract details of communicating over a protocol and to provide a byte stream interface to communications occurring over the protocol, while removing protocol specific code from an application program. The method includes creating an instance of a protocol object from a source of registered protocol handlers based on a request to communicate over a protocol and using a base class API to communicate over the protocol through the protocol object.

Claims

1. A data packet adapted to be transmitted between two or more computer processes, the data packet comprising:

information operable to facilitate selecting one from a plurality of protocol object creators.

2. A data packet adapted to be transmitted between two or more computer processes, the data packet comprising:

byte stream data produced by a protocol object, the byte stream data having at least one of a format specific to a protocol and one or more headers and/or footers specific to the protocol removed from a first data read from a resource.

3. The data packet of claim 2, further comprising:

a second data having at least one of a format specific to the protocol and one or more headers and/or footers specific to the protocol added to a byte stream provided by a computer program.