HTTPR

When request-response style SOAP messages are used, the HTTPR rules for response matching to specific requests must be followed.

SOAP and JMS are two examples of application messaging interfaces for which reliable delivery using the HTTPR protocol can be provided.

Listing 2 shows a full example of what a WSDL specification for a SOAP message using HTTPR would look like.

Exactly how this works is beyond the scope of this discussion.

The SOAPAction parameter is carried in the HTTPR message context header as the type app-soap-action.

The messages, and any accompanying meta-data, are uninterpreted bytes as far as HTTPR is concerned and are assigned no other meaning by it.

To this end we recommend that a protocol layer be added to HTTP that we call HTTPR and similarly to HTTPS that we call HTTPSR.

Each batch is assigned an identifier by its sender (either client or server) that is sent along as HTTPR metadata with the batch.

HTTP version 1. 1 serves as the base upon which HTTPR builds its reliability.

Draft of HTTPR specification (a new protocol for the reliable transport of messages over the HTTP 1. 1 protocol)

Listing 2: A WSDL specification for a SOAP over HTTPR service

HTTPR: a protocol for reliable messaging over HTTP

will reference this HTTPR binding, and the service port address location will be an HTTPR uri. For example