Archived
This forum has been archived. Please start a new discussion on GitHub.
.NET AMI api vs TPL
Hi,
Ice version: 3.5.0
.NET 4.0
Instead of making calls via AMI from the client, the approach we have taken is using Task (Task Parallel Library) constructs for making the server calls asynchronously.
Do you see any pitfalls using this approach?
Do you strongly suggest that we use the ICE AMI APIs as oppose to TPL?
Please advise.
Ice version: 3.5.0
.NET 4.0
Instead of making calls via AMI from the client, the approach we have taken is using Task (Task Parallel Library) constructs for making the server calls asynchronously.
Do you see any pitfalls using this approach?
Do you strongly suggest that we use the ICE AMI APIs as oppose to TPL?
Please advise.
0
Comments
-
Hi,
Using a Task for making Ice synchronous calls to servers is fine if it simplifies your code and if your code is not performance sensitive.
Otherwise, AMI calls should in theory be a bit cheaper since they don't require switching to another thread for sending the request and waiting for the reply (Task are executed by the .NET thread pool).
Cheers,
Benoit.0
