Performance of asynch twoway vs oneway proxies
We have a client that is overwhelming the server with oneway calls on certain conditions, and are trying to limit new invocations by changing to twoway asynch calls so we can get a confirmation the server has serviced old calls.
Our goal to is track the number of outstanding invocations on the proxy, and stall if there are too many. Once enough tasks are stored, we will task->waitForComplete(); before making the next invocation. IE: Once 30 calls have been made you must wait for the first once to have been completed before sending 31
This is how it was:
Here's the changed version:
auto task = twoway->begin_call(); task.waitForSent();
Do these two tasks behave the same way in regards to performance and throughput?