perfsonar development work

["Vedrin Jeliazkov" <>]

Hi Jeff, Joe, Maciej, All,

"Jeff W. Boote" 
<>
 wrote:

<snip>

> Suggestions from GUI developers about what types of queries they intend to
make
> 
> (what information they need) would be very helpful. I just have not been 
> thinking along these lines lately.

There might be several different queries, as described below (in increasing
order of complexity and expected performance impact);

1) get the addresses of services, registered in the LS;
2) get the addresses of services, registered in the LS and having a given type
(e.g. utilization MA, Hades MA, etc.);
3) get the addresses of services, registered in the LS, having a given type
and providing info for a given data point (e.g. IP interface address);
4) get the full list of data points for a given service;
5) get the full list of data points for all registered services;

Query (1) is mandatory. Query (2) would be perhaps sufficient for making the
current MA.conf in perfsonarUI obsolete. Query (3) would greatly simplify (and
probably make faster) path visualization, because the clients would not have
to query a range of other services for each successive hop. Queries (4) and
(5) might be desirable in some cases (e.g. when drawing maps), but perhaps
they could be run much less often, because of the expected performance impact
on the LS itself.

Kind regards,
Vedrin