What feature would you like to see most in Ice?

[marc]

Originally Posted by feathers

Three years have passed since the above statement was made. Today, a google of IPv4 yields 9M hits. A google of IPv6 yields 16M hits.

Does ICE now support IPv6? (I searched the PDF version of the ICE 3.2.0 manual, but found no reference to IPv6.)

No, Ice does not support IPv6. So far no customer has ever required this feature, therefore we have not implemented it.

[feathers]

"If you build it, they will come." - Field of Dreams (1989)

[matthew]

"Show me the money" - Jerry Maguire (1996)

[dhlong]

SSL support in ICE-E !

[CatOne]

Originally Posted by matthew

"Show me the money" - Jerry Maguire (1996)

Matthew, always with the riposte

[pgquiles]

This "feature" is not exactly about Ice but about its Windows installer. Please, make it create an actual folder under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Uninstall (or event better, under HKEY_LOCAL_MACHINE\Software\ZeroC). Currently the folder name under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Uninstall is autogenerated (or it looks like that), making it impossible to reliable find the location of Ice.

Thank you.

[solikhin]

I think it would be great if ICE support transaction (I mean database transaction, two phase commit like setcomplete() / setabort() feature in DCOM /COM+, or Java transaction). It will promote ICE as direct replacement of Microsoft COM+, but run on multiplatform.

[sly596]

I, too, would love to see Event Filtering for IceStorm. It is such a fundamental necessity in an event channel.

Pete

[epeisach]

I have a simple client model for periodically reporting some statistics on a machine.
Given that the machines already have rpms for Ice in python on the machine, using loadSlice() is appealing in that I will not have to regenerate any files if the rpms are upgraded and slice2py requires some changes.

loadSlice is nice - in that I can parse a slice file - but it requires an additional file to be distributed with this otherwise one file client. It would be nice if there was an equivalent to loadSlice that would parse a string and not just a file... I could probably hack it up to have the python script create a temporary file and dump the contents there for parsing - but as I said - a hack....

Looking under the hood - this would be a non-trivial change...

Ezra

[paolo]

A big problem with Ice is tracking object lifetime for object created and owned by clients. Tipically this objects are created by Factories with UUID Identity and the responsability to destroy them is leaved to the client. What happen if a client doesn't destroy them (for network problems or bugs)?
It wuold be very nice to be able to register object with timeout. An object adapter able to destroy object not accessed for a configurable period of time.

[xdm]

Hi paolo,

You can already do that with a Timer in your servant implementation, i think
that there is no need for such a change, there are lot´s of diferent scenarios for objects life time and no one is better for all kind of applications, is better implement it in the application layer.

There are several examples in Ice sources of how do what you describe.

look at demo/Ice/session , demo/Glacier2/chat in Ice sources
Also is interesting the Article "The Grim Reaper: Making Objects Meet Their Maker" wrote by michi in newsletter 3.

http://www.zeroc.com/newsletter/issue3.pdf

Hope this help