CPU Idl is very high

[dragzhb]

HI marc:

I have tested that oneway method almost 80% quickly than twoway, could you add oneway option in AMI and AMD in furture? beacuse with TCP/IP, It has high reliable transfer. I think we would need more and more speed in many place(eg. in telecom), not only stable

[marc]

Oneway is faster than twoway, because no response is being sent, meaning that the client just pushes the data on the TCP/IP stack, and then moves on to other things without waiting for the server to respond.

AMI is defined as having the response from the server delivered asynchonously (in a callback). Since in the case of oneways there is no response, there is also no point in sending a oneway call with AMI.

For AMD calls, you can receive oneway calls and twoway calls, it doesn't matter to the AMD server implementation.

[dragzhb]

HI marc:
Thanks for your response, but I have another question of AMI .
I think AMI should implment as oneway call, why? I think AMI shoul send data in one thread, and it will quickly return , and another thread receive data from server and call callback function. it's mean send data and receive data thread must be two thread , not one thread , if you only have one thread to send and receive data,when you sent data and wait for receive data and when you received data ,then invoke callback function, I think that it's not asynchronous invoke, it's maybe synchronous invoke? is it right?
I have printed out the thread ID, I have found callback class's thread is different than sending data thread, but I can't confirm receiving data thread

[marc]

That's already the case. The caller thread sends the data, but doesn't receive the response. A thread from the client-side thread pool receives the response and invokes the callback.

[dragzhb]

I see, thanks