[Spread-users] Spread in distributed URL monitor application

Jacob Green jgreen at spreadconcepts.com
Thu Mar 3 08:51:23 EST 2005

Spread can handle WAN networks.  Both in daemon to daemon traffic (UDP) and
daemon to client traffic (TCP/IP).  However, since daemon to daemon traffic
is UDP, it requires any firewalls be open for those ports.  Furthermore if
IP NATing is going on, it gets a lot more complicated.  This may or may not
be the case with the cable modems you are using.

Alternatively, just have the client monitoring programs connect to Spread
via TCP/IP and don't run daemons on them.  Run the daemons on fixed publicly
accessible IP machines you control.  This avoids any firewall/NAT issues.  


-----Original Message-----
From: spread-users-bounces at lists.spread.org
[mailto:spread-users-bounces at lists.spread.org] On Behalf Of Mike M
Sent: Wednesday, March 02, 2005 10:42 PM
To: jgreen at spreadconcepts.com; spread-users at lists.spread.org
Subject: Re: [Spread-users] Spread in distributed URL monitor application

On Wed, 2 Mar 2005 11:56:26 -0500, Jacob Green
<jgreen at spreadconcepts.com> wrote:
> Monitoring "App 1" detects a dead URL, announces it to a Spread Group X.
> Other monitoring apps are listening to Group X, and once they receive the
> dead URL message from App 1, each attempts to connect to the URL.  They
> announce their results back to the private group of App1.  Once App 1 has
> collected enough results from the other apps (say it take 3 confirmations
> declare a URL dead), it will then send out the e-mail you spoke of.
> Many other options, examples, etc are quite possible.  Including handling
> the case were connectivity between monitoring apps is down.
> Jacob

This is exactly the program flow I had in mind.  Any ideas how to get
it started? :)

Seriously though, I think the spread toolkit might just be the trick
for the messaging subsystem for my monitoring app.  If you know if any
perl sample code I can get my hands on, that would be great - I
haven't had much luck finding scripts using spread on the Internet.

Also, is spread suitable for use over high-latency WAN/Internet links?
 Since the monitors will mostly be running on desktop linux boxes
connected to cable/DSL connections, are there any caveats to this sort
of implementation?

Thanks for your input!


Spread-users mailing list
Spread-users at lists.spread.org

More information about the Spread-users mailing list