Request/Response definition

Request/Response. Used when an initiating party requests information that a responding party already has and when the request for business infor- mation requires a complex interdependent set of results. • Data Exchange:Allows a partner, industry or community to define a spe- cific Business Transaction pattern that is not in the concrete set. The semantics used for data exchange are partner-specific. • Legacy Business Transaction:Retained in v2.0 and v2.0.1 technical spec- ifications for conversion purposes only to enable the user community to migrate to the concrete patterns. This pattern is not recommended for use for the concrete Business Transaction patterns. An ebBP definition references, but does not define, a set of logical Business Documents. It is important to note that the ebBP technical specification focuses on the logical Business Document not a wire format and hence has nothing to do with the ebXML Messaging Service (ebMS) message envelope (SOAP with Attachments) which is wire format.
View Source
Request/Response means the offer submitted by the Contractor to supply the Goods and/or Services made in response to a Principal Request.
View Source

Examples of Request/Response in a sentence

  • Suppliers that can receive OrderRequest documents and send various messages or initiate Request/Response transactions describe their OrderRequest support in the profile transaction.

  • Request-Response Model‌ Request-Response transactions can be performed only over an HTTP or HTTPS connection.

  • This document does not strictly follow the Request/Response paradigm; its use will be explained in detail.

  • Protocol Specification‌ There are two communication models for cXML transactions: Request-Response and One-Way.

  • The CURES web service will support two patient search use cases: • Query Use Case 1 – Single Request/Response o Use Case 1 follows the NCPDP standard where every search patient request returns either no match or a single match.

  • One-Way (Asynchronous) Model‌ Unlike Request-Response transactions, One-Way messages are not restricted to the HTTP transport.

  • The following figure shows an example of how A and B might communicate with messages instead of the Request-Response transaction.

  • For example, assume that a threat scenario representing initiation of a HTTP Request/Response splitting is included in a risk model for client-server protocol manipulation.

  • When a Request-Response transaction initiates a “conversation” through multiple one-way interactions, the first message can include the payloadID of the most recent relevant Request or Response that went in the other direction.

  • Page 2 of 5 The CURES web service will support two patient search use cases: • Query Use Case 1 – Single Request/Response o Use Case 1 follows the NCPDP standard where every search patient request returns either no match or a single match.