Client Web Service HTTP Tunnel 1 2 Synchronous Message BLK

Asynchronous Message on Same HTTP Socket Client Web Service HTTP Tunnel 1 2

Async Message on different Socket Client Web Service HTTP Tunnel HTTP ACK

HTTP Tunnel Stack Handling of Synchronous Messaging Generated Java Code Shell for ( … ) Public Class EchoService1 { public Service1EchoResponseType echo(Service1EchoRequestType body) { Service1EchoResponseType oResponse = new Service1EchoResponseType(); return oResponse; } Stack Infrastructure to Receive Message Custom Method Implementation Stack Infrastructure to Send Reply Message Request Message Response Message Responding Gateway

HTTP Tunnel WS-Addressing Asynchronous Messaging as Managed by Web Service Stacks Generated Java Code Shell for ( … ) Public Class EchoService1 { public Service1EchoResponseType echo(Service1EchoRequestType body) { Service1EchoResponseType oResponse = new Service1EchoResponseType(); return oResponse; } Stack Infrastructure to Receive Message Custom Method Implementation Stack Infrastructure to Send Reply Message Request Message Response Message HTTP Ack In all stacks – return from method triggers the response. Initiating gateway is not blocked. Responding gateway has long running process until the return from the method Responding Gateway Be nice if… Could pause running implementation and queue the message. Resume when message is processed. Technically this “suspension” in the stacks is not possible. Sleep – leaves process running.

HTTP Tunnel Stack Handling of Async Messaging – 2 Separate Services - Responding Gateway does NOT Block on Latent calls Generated Java Code Shell for ( … ) Public Class EchoService1 { public AckResponseType echo(EchoRequestType body) { AckResponseType oAck = new AckResponseType(); return oAck; } Stack Infrastructure to Receive Message Custom Method Implementation Stack Infrastructure to Send Reply Message Request Message Response Message Response Ack Application to process request (Could have manual and automated steps) Send Response through Web Service Call Queue Response after message queued. Both Server and Client – no longer blocked Could still use “RelatesTo” field in WS-Addressing to associate Message ID