Re: [JXTA dev] Discovery Service x Propagate Pipe

I am not sure using a propagate pipe for discovery is any better than 
discovery.  Propagating a message results in walking the message the 
full length of the peerview, and to each subscriber of the pipe, whereas 
a discovery query may not go further than it's rendezvous, and at worst 
case replica + destination.

Can you describe the problem or the end goal, there may be alternatives 
to suggest.


Mohamed


Edward Ribeiro wrote:
>
> I am designing an application where each peer keeps calling 
> getRemoteAdvertisements( )
> from time to time (2 min.) so that it can be notified as soon as other 
> peer publish a query
> Adv. I don't like the idea of issue such a query because it floods the 
> network, doesn't it?
>
> I just came up with the idea of using a well-known propagate pipe that 
> everybody listens
> to. A peer that want to issue such a query can make use of this pipe 
> and issue the query
> some times down the pipe.
>
> What do you think about it? It can be a nice solution to a largely 
> distributed application or
> I should stick with getRemoteAdvertisements( ) calls?
>
> Thanks,
> Edward


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