> -----Original Message----- > And the async will also affect the transport part, right?
Hi James, Actually my intention was that the transport Conduit would be oblivious to the invocation style, i.e. instead of the ClientTransport providing the Future as was the case in the old Celtix transport APIs, this logic would be pushed up into the org.apache.cxf.endpoint.Client. IMO the transport shouldn't be concerned with how the application developer chooses to rendez-vous with the response, whether synchronous or async. The work done by the transport in order put the request on the wire and pull the response off is the same in both cases. /Eoghan
