Originally posted by xiehua now Ice can use either tcp/ip or UDP as a transport.
If Ice can use http also as a transport,It is so useful.
In my country,always the computer client connect to the
internet through a proxy server that only support http.
So the client with Ice can't work in this case.
Originally posted by peter.s i very much would like to see if Ice would have some build system instead of the config/Make.rules system.
especially the autotools framework comes to my mind because with this framework dependencies can easily be tracked and various platforms can easily be checked and supported.
i'm currently trying to run Ice on 64bit alpha linux and 32bit ppc linux and perhaps soon on mipsel linux and autotools would make this job much easier ;-)
Originally posted by marc The problem is that (to my knowledge) there is no official standard yet for reliable multicast, as there is for reliable unicast (TCP). Ice doesn't aim to try to invent basic internet protocols, but rather to put our object model on top of existing and proven protocols (like TCP or UDP).
Originally posted by damingyipai Can ICE support WebService by it-self? that can give me more time in my logic coding...
and, how to use slice2wsdl?
Originally posted by marlowa The NORM implementation I looked at is portable and requires no kernel mods. Take a look at http://norm.pf.itd.nrl.navy.mil for more details.
Originally posted by Yunqiao Yin Provide more communication protocol options,such as:
Unix Domain Socket,Shared Memory,etc.
Originally posted by griffima ICE provides an at-most-once messaging delivery guarantee. Is there a plan to implement exactly-once (guaranteed) delivery- or perhaps you feel that this is better implemented at a different abstraction layer? Where/how (in general) would you implement it? At the moment it does not appear as though the lack would be a dealbreaker as far as implementing ICE as a middleware solution but I'd like to at least know if there's a good solution in case it comes up again.
Originally posted by griffima Yes, I was referring to a persistant message queue.
Originally posted by mep For ICE for C#, many cannot afford a copy of M$ VS.net. But since .Net framework SDK is free, which include C# compiler and nmake. Why not supply makefiles for nmake, as well as VS project file.
Originally posted by chenhong_sz All Ice Service(IcePack,IceBox,IceStrom...) can been build with user Application together,then these service can been run in different style: console, service(deamon),GUI Application.
as i know, TAO's corba service is doing so.