Maybe one description in Ice Manual is not corrent

[rc_hz]

Ice 3.1.1 Manual, Page 818:

Method: ice_locatorCacheTimeout
Description: For indirect proxies, returns a new proxy with the specified timeout. ...

[michi]

I'm not sure what you mean here. What do you think is wrong?

Cheers,

Michi.

[rc_hz]

It seems that the description of ice_locatorCacheTimeout(...) is the same with the description of ice_timeout(...):

Ice 3.1.1 Manual, Page 818:
Method:ice_timeout
Description: Returns a new proxy with the given timeout value in milliseconds.

However, I think that ice_locatorCacheTimeout(...) just affects the lifetime of the resolving results of indirect proxies,for example:
myobject1@myadapter1 ----> myobject1:tcp -h 10.10.10.1 -p 10001 ----> lifetime: 10 minutes
myobject2@myadapter2 ----> myobject2:tcp -h 10.10.10.1 -p 10002 ----> lifetime: 20 minutes
That is, ice_locatorCacheTimeout(...) is not an invocation timeout.

[michi]

Thanks for that, we'll look at improving the doc for the next release.

Cheers,

Michi.

[bernard]

There is a better explanation of what this function does in the "Ice.Default.LocatorCacheTimeout" entry:

Ice.Default.LocatorCacheTimeout
Synopsis
Ice.Default.LocatorCacheTimeout=num
Description
Specifies the default locator cache timeout for indirect proxies. If num is set to a value larger than zero, locator cache entries older than num seconds will be ignored. If set to 0, the locator cache won't be used. If set to -1, locator cache entries won't expire.

Each entry in the client-side "locator cache" has an associated timestamp, and when you invoke on an indirect proxy, Ice checks this timestamp against the "locator cache timeout" of the proxy to see if can use the cached entry or if it needs to resolve the indirect proxy using the (remote) Locator.

Cheers,
Bernard

[rc_hz]

There is a better explanation of what this function does in the "Ice.Default.LocatorCacheTimeout" entry:

Ice.Default.LocatorCacheTimeout
Synopsis
Ice.Default.LocatorCacheTimeout=num
Description
Specifies the default locator cache timeout for indirect proxies. If num is set to a value larger than zero, locator cache entries older than num seconds will be ignored. If set to 0, the locator cache won't be used. If set to -1, locator cache entries won't expire.

Each entry in the client-side "locator cache" has an associated timestamp, and when you invoke on an indirect proxy, Ice checks this timestamp against the "locator cache timeout" of the proxy to see if can use the cached entry or if it needs to resolve the indirect proxy using the (remote) Locator.

Cheers,
Bernard

Yes, this is a very precise explanation. Thank you very much!