Discovery Service x Propagate Pipe

------=_Part_3400_540969.1127179435972
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I am designing an application where each peer keeps calling=20
getRemoteAdvertisements( )
from time to time (2 min.) so that it can be notified as soon as other peer=
=20
publish a query
Adv. I don't like the idea of issue such a query because it floods the=20
network, doesn't it?

I just came up with the idea of using a well-known propagate pipe that=20
everybody listens
to. A peer that want to issue such a query can make use of this pipe and=20
issue the query
some times down the pipe.

What do you think about it? It can be a nice solution to a largely=20
distributed application or
I should stick with getRemoteAdvertisements( ) calls?

Thanks,
Edward

------=_Part_3400_540969.1127179435972
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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

------=_Part_3400_540969.1127179435972--