ws-muse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject RE: Issue in EndpointReference.equals() method
Date Mon, 28 Apr 2008 09:19:25 GMT
I agree with the reason:

        // compare wsa:Address - EXCLUDING the host. this allows us 
        // to compare EPRs that have equivalent IP addresses and 
        // machine names/localhost

given that localhost could also be the machine name and the ip address,
or be multi homed.  

However it seems to be perfectly valid to run the same client (with
presumably the same url source path) from two seperate machines or
indeed multiple clients from a single machine.

Its exceptionally difficult to make hostname lookup work in general but
I think its a valid enough requirement for the client to provide a
decent hostname:

InetAddress addr = InetAddress.getLocalHost();
shouldn't be that hard to use.

And IF need be have a simple rule for "localhost" vs the actual local
host name and default interface.  For multi-homed servers/clients its
normal to require them to choose an IP address / hostname.

Its a simple fix but there may be something I've overlooked.

PS (thanks for finding this Eitan, I'll certainly be fixing it on my
local version)

-----Original Message-----
From: Eitan Plotnik [] 
Sent: Monday, April 28, 2008 10:49 AM
Subject: Issue in EndpointReference.equals() method

I have a test client registering for notifications.
When I run the client from 2 different machines at the same time, using
the same server, some of the notifications are sent to the wrong client.

I noticed that EndpointReference.equals() method explicitly doesn't
compare the IP address part.

Does the test client must generate a unique (machine based? timestamp?)
subscriber uri part after the IP address?

View this message in context:
Sent from the Muse - Dev mailing list archive at

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message