Discovery Service x Propagate Pipe

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