Originally posted by marc We would like to get a feeling for what features are on top of your wish list. So, what features are you missing in Ice?
Please feel free to suggest anything that comes to your mind, including, but not limited to, new language mappings, new services, new core features, documentation enhancements, etc.
Originally posted by chaukmean Right.
But a reliable multicast for delivering ICE requests can be built on top of UDP multicast.
Originally posted by chaukmean What about RT CORBA like features ?
Originally posted by marc Yes, of course it could. But I simply don't feel that Ice is the right abstraction level for doing this. I would much prefer to use an existing reliable multicast protocol and add it to Ice as a protocol plug-in.
Originally posted by marc This would be a very good addition to Ice, and it's on our TODO list. The reason why I started this thread was to find out what is most important to Ice users, and to adjust the priorities on our TODO list accordingly.
Originally posted by chaukmean JavaGroups offers reliable multicast communication. CORBA will offer the same kind of feature with ROMIOP (Reliable Ordered Multicast Inter-Orb-Protocol). I hope you will change your mind and that ICE will support in the near future a reliable multicast communication.
Originally posted by Ctaesis I'd like to see a big darn example Ice project that does something reasonably useful, and integrates the various existing features in non-canned ways.
Originally posted by silmaril A bit late to get it for this project, but I would very much like to see a mapping for Python in the future.
Originally posted by alexander Seriously, I'd like to see that Java implementation has the same or close functionality/number of implemented features as C++ one.
Please, don't forget about IceJ.
Originally posted by mes Can you be more specific?
The Java implementation is just as important to us as the C++ implementation. The feature set of the two was determined very deliberately: we try to provide the same feature in both, unless there's a platform limitation that prevents it, or a compelling advantage (such as performance) that favors an implementation in only one language.
As one example, it's not currently possible to implement IceSSL in Java due to JDK limitations. As soon as the JDK allows it, we will implement IceSSL in Java. Another example is a service such as IcePack, which (in our opinion) is more appropriately written in C++ given its responsibilities.
Originally posted by rcerq But I need some sort of DII, DSI and IFR!
Originally posted by Claes a C# version on MS .NET and Mono .NET is definitely highest on my wish list. Secondly, a UML(XMI) --> Slice mapping.
Originally posted by Ctaesis Did you run into some issues with the C# mapping? There's a post around here with Michi implying that C# would come in the Feburary update. I'm not pushy, really.
There are several issues with some C# libraries being very buggy, such as the network library
Originally posted by damingyipai Can ICE replace the CORBA at short time? If not, this feature is important.