After doing some more research, I think at this point I should reformulate my question... What I really want to understand is this:
How does the standard NON-async transport (cxf-rt-transports-http) work on the client for Async methods with callbacks? Looks like it doesn't just queue outstanding requests (when there are more than 24 of them). It's much smarter than that. Because if I have 50 requests or more, all of them are sent to the server at the same and come back at the same time, even though there are only 24 active threads. What magic does it do? Especially for sending the requests. I could look at the code if I knew where to start... I think understanding how it works will help me understand the difference between "transports-http" and "transports-http-hc" and will make it more clear when to use which. -- View this message in context: http://cxf.547215.n5.nabble.com/Async-transport-performance-using-cxf-rt-transports-http-hc-tp5751832p5751949.html Sent from the cxf-user mailing list archive at Nabble.com.
