Archived
This forum has been archived. Please start a new discussion on GitHub.
Newbie question : ICE with .NET
Apologies for the general nature of this question. I am looking at ICE for use in a .NET environment for a distributed printing applications. It is a mixed C/C# code base. I am interested in people's experience with ICE in a .NET context and their reasons for choosing ICE over other approaches. If you prefer to contact me direct you can, on dunwin@bing.com.
Duncan Unwin
Duncan Unwin
0
Comments
-
Apologies for the general nature of this question. I am looking at ICE for use in a .NET environment for a distributed printing applications. It is a mixed C/C# code base. I am interested in people's experience with ICE in a .NET context and their reasons for choosing ICE over other approaches. If you prefer to contact me direct you can, on dunwin@bing.com.
Duncan Unwin
Well, what are the choices, if you want to communicate across platforms?
- CORBA:
Read Michi's comparison with ICE.
- DCOM:
Deprecated.
- Web services (SOAP or REST):
Only useful for coarse grained interfaces (due to overhead).
Not as standardized as one might think - they even had to create
a standard within the WS series of standards called WS-I
(I for interoperability) to address the issues.
- .NET Remoting + Java RMI with bridge software:
Have to buy extra commercial software. Licenses are not cheap.
Only works .NET <--> Java
- ICE:
Tested .NET against Java - it simply works. There were a few code
generation issues but they have been fixed - obviously the .NET
implementation had not been used as heavily yet to iron out all the issues.
In my case it enabled me to expose a vendor provided and somewhat
non-standard SOAP web service in a way that everyone could use.
Karl0