Re: how can make searching for peers on jxta more accurate?
Bruno Margerin <[email protected]> Wed, 28 Sep 2005 19:09:50 -0400
| Newsgroups | gmane.comp.java.jxta.user |
|---|---|
| Message-ID | <[email protected]> |
Mike, Could network optimization in JXTA 2.3.5 then explain why the discovery service, when queried for PeerAdvertisement, only returns the RDV/ SuperPeer Peer Advertisement. By returning solely the RDV/ SuperPeer Peer Advertisement, JXTA not only answer the generic query for PeerAdvertisement but also has the lowest network load. I understand that it is what JXTA is aims at. Maybe your answer to that posting also answered the question I asked in the posting I wrote a little earlier "JXTA 2.3.5 New Peer Discovery Behaviour". If so, how should I proceed to get a even partial, but reasonable list (or even a count) of peers that are within a peer group? Can you make a "edge peer" Advertisement query to the discovery service? Thanks, Bruno Mike [bondolo] Duigou wrote: > sparky123 wrote: > >> how can make searching for peers on jxta more accurate? >> >> reagards >> helpastudent > > > It sounds like you are probably asking the wrong question. The JXTA > discovery service does not provide exhaustive search services. It will > never return *all* of the peers on the network, for example. The > discovery service is instead intended to provide a reasonable number > of advertisements matching the query while doing the minimum amount of > work on the network in order to satisfy the query. > > So, if you issue a broad query for peers the discovery service will > indeed return some results, but if it can do so by only querying your > neighbour peers then it will not look further. If you issue a narrow > query, exact peer name for example, that cannot be answered by the > local peers then the JXTA discovery service will look harder across > the network in order to provide an answer. > > Hope that helps. > > Mike > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >