[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Problem with Service Endpoint matching when using different network names

On 7/27/2018 7:22 AM, Peter Hermsdorf wrote:

Hi Scott,

that sounds and looks really promising! I'll need some time to process the information you gave and look at the code and then come back to you.


This morning I've added some code to allow properties to set the hostname and port on server side, and to use the ecf.endpoint.id on client side to connect to the given hostname and port.ÂÂ This is working...see TCPSocketServerContainer and TCPSocketClientContainer classes.


I've been testing localhost with the LAN-based discovery (zeroconf) so the hostname/port exported in the endpoint description is what is used on the client.ÂÂ If/when other discovery and import is used on the client, then it can do whatever it wants wrt what hostname and port to use to connect to the server.

There are some ways that this is limited, but it can be generalized or extended, and I'm hoping it will give a good idea of how to create others.

Scott