views:

60

answers:

1

We have the follwing situation:

The clients are sending events / messages to the server over a webservice. The server can identify the clients according to the "Sender URI". The server must distribute now the message to the "interested listeners".

Now it can be that a client says he is e.g. http://127.0.0.1:8000/ on the server this client is configured with http://localhost:8000. Uri.Compare( ) and Uri.Equals return both false.

Does anybody knows an alogrithm who can identify the URI with all it's representations? I mean Localhost == 127.0.0.1 == "Real IP" == "DNS-Name" ?

Thanks Thomas

A: 

Because nobody has posted an answer yet, I will stay with my own made "algorithm" / method which tries to compare all different representations.

What I found out: At the server it is not possible to determine in all cases a remote URL. It can be that the user - account or the subnetwork the server is in, does not have enough priviledges to determine e.g. which IP is behind the Active Directory Name.

So there will be always the problem that the server needs a manual filled file or so, which he uses as a base to determine if he knows the sender-URI

TomTom