name.Endpoints semantics

[mwilson]

If I specify (in a configuration file) an endpoint list, for example:

MonitorAdapter.Endpoints=tcp -h curly -p 10000:tcp -h curly -p 100001: ...

Does this mean that seperate invocations (separate processes) of a client fed that configuration file will use port 10000, 10001, etc.? Or does it mean that the endpoints will be used sequentially within a given process as adapters are created?

Is there a way to have an object adapter select its own port?

Thanks!

[mes]

Does this mean that seperate invocations (separate processes) of a client fed that configuration file will use port 10000, 10001, etc.? Or does it mean that the endpoints will be used sequentially within a given process as adapters are created?

The property you've defined causes the adapter to create several endpoints. Normally this is only necessary when you have special requirements. For example, when you need endpoints that use different transports, or for endpoints that are on individual network interfaces.

You'd only be able to execute one process at a time with this configuration on the same host, since the ports will already be in use by the first process.

Is there a way to have an object adapter select its own port?

Yes, if you leave off the port, the object adapter will ask the operating system to pick one for it. The implication is that subsequent invocations of the program will most likely use different ports, and therefore any proxies created by the previous incarnation of the program are no longer valid.

- Mark