Re: JXTA 2.3.5 New Peer Discovery Behaviour

if there are in fact other peer advertisements on the rendezvous and all 
that is returned is a single advertisement then it is possible a 
regression was introduced in 2.3.5 (file an issue if such is the 
case).   Otherwise you are witnessing the results of issue1404, and 1405.

Mohamed


Bruno Margerin wrote:
> Hi,
>
> I've recently updated my software to JXTA 2.3.5 and I've noticed a 
> changed of behavior as for the discovery service in relation to the 
> Peer Advertisement.
> Before (when using JXTA 2.3.4 I think), when querying for Peer 
> Advertisement ( 
> disco.getRemoteAdvertisements(null,DiscoveryService.PEER,null,null, 
> 100); )
>
> I would get edge and super peers  PeerAdvertisement response.  
> However, Once I upgraded to JXTA 2.3.5, I only get a  Peer 
> Advertisement response from the super peer.
>
> I originally would Query for Peer Advertisement  ( 
> disco.getRemoteAdvertisements(null,DiscoveryService.PEER,null,null, 
> 100); ) wait a bit  and look into my local cache for Peer 
> Advertisement. Then I also followed the JXTA programmers' guide and  
> Registered a Discovery listener, Queried  for Peer Advertisement  ( 
> disco.getRemoteAdvertisements(null,DiscoveryService.PEER,null,null, 
> 100); )  and tried to extract the Peer Advertisements out of the 
> DiscoveryEvent. Both works with the previous of JXTA, but  as for JXTA 
> 2.3.5 I still only get  the PeerAdvertisement for the superpeer / RDV, 
> not the other "Edge Peers".
>
> What are the "best practices" as for discovering peers on JXTA 2.3.5?
>
> Thanks,
>
> Bruno
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>


-- 
http://blogs.sun.com/roller/page/hamada
http://weblogs.java.net/blog/hamada