|Re: [ecf-dev] Problem with Service Endpoint matching when using different network names|
thanks for your suggestions.
I'm afraid to say that this does not solve all issues for us.
If i understand you correct, you were describing different ways to change the service endpoint on the server to match the one that the client uses to connect to the exported service on the server.
The problem is, we have setups where different client machines use different network names to connect to the same server instance. e.g.. clients in the local network of the server can use a local DNS to connect to the server by a locally known host name. We have other clients connecting via a remote network (VPN tunnel) and sometimes we can't use the local DNS setup trough that tunnel, but just the IP address or a completely different hostname for network configuration reasons.
I think what we need is a completely hostname (and port) agnostic
way to match the service endpoints between the client and the
In other words: one thing is to define the network target (by
hostname or IP and port) and the other thing would be to match the
remote service once the client and server are connected by network
(via the service name and version etc.).
I'm willing to implement some code to do that, if you could point me in the right direction....
Am 21.06.2018 um 19:14 schrieb Scott Lewis: