<html>
A concern I'd have with that approach is the requirement for CORBA on all
the clients... is the orb something that is available in all the JVMs?
Can you redistribute the jars for it? How does it handle the network link
to the server coming and going?<br>
<br>
On the topic of the beacon ...<br>
<br>
I've put a hack into the beacon server that writes a text-format dump of
the server state once per minute. You can find this at<br>
<br>
<x-tab> </x-tab><a href="http://www-unix.mcs.anl.gov/~beacon/table.out" eudora="autourl">http://www-unix.mcs.anl.gov/~beacon/table.out</a><br>
<br>
For the folks wanting to do archiving of beacon data, this should provide
a means for getting the raw data. The format should be pretty
self-explanatory; the tuples of data at the cross points are loss rate /
delay / jitter/ out of order/ duplicates. The tuple is preceded with an
"S" if the entry is stale (grey cell).<br>
<br>
There is a php-based viewer available that allows the selection of a
subset of the beacons to view, either by node name or by beacon name.
This is at <br>
<br>
<x-tab> </x-tab><a href="http://water.mcs.anl.gov/~olson/beacon.php" eudora="autourl">http://water.mcs.anl.gov/~olson/beacon.php</a><br>
<br>
This location will likely change at some point, but is up and working
now.<br>
<br>
If you run an AG node and are not listed in the list of nodes, send me a
note with your beacon name and I'll add you.<br>
<br>
This interface currently only shows the loss rates. Anyone who's
interested in adding more support, let me know and I'll send you
the php code to modify. (I've already spent more time puttering with this
than I probably should :-)<br>
<br>
--bob<br>
<br>
<blockquote type=cite cite>Iam presently working on a program that
permanently fixes the scalability<br>
problme in Beacon viewer.<br>
Iam trying to use the distributed object paradigm for the
beacons.Iam<br>
currently using Visibroker's ORB to do that<br>
We can run a event channel in which all the events of beacons will
be<br>
registered essentially i want to implement the Mediator pattern for
the<br>
beacons.So the beacons that register for these events can get the info
of<br>
other beacons.<br>
Beaconviewer will just be another client which registers to all the
events<br>
that the beacons in the channel generate.<br>
BeaconServer initialises the ORB and all the beacons get the instance
of<br>
the ORB thro the BeaconClient <br>
The BeaconClients will also register to the EventChannel<br>
<br>
Any ideas would be greatly appreciated<br>
<br>
Ravikiran<br>
On Fri, 9 Mar 2001, Robert Olson wrote:<br>
<br>
> And the memory problem fix may also fix this ...<br>
> <br>
> At 04:24 PM 3/9/2001 -0600, Tony Rimovsky wrote:<br>
> >However, I<br>
> >haven't emphasised it with DAST because the memory problem they
are<br>
> >trying to track down is more important overall.<br>
> <br>
> </blockquote></html>