perfsonar development work

[Martin Swany <>]

Hi Michael,

> It is expected that services will use the api in the future. I'm  
> also not
> aware of any ps services currently using it.

I hope that more services start to use it.  Most of the perfSONAR-PS
components use the perl API as it is easier to use.  Even more to the
point, we have been talking in very early terms about augmenting the
LS/TS in various ways to improve performance and we had started to look
at the Java API to study how easily we could make those changes without
impacting existing services.  This thread is timely as we really need to
engage the entire perfSONAR community (as you note below.)

> Likely use-case is that a
> service will lookup topo-service for configuration of the service  
> itself.
> Other possible use-cases of the top of my head are:
> - to find a lookup service to register themselves against :-)
> (or some other form of auto configuration)
> - to find cooperating services that contain information for drilling  
> down
> (though this might be something that could be handled in the client  
> layer)
> - to find other services that the services can use for collecting/ 
> processing
> data.
> etc.

I think these are all great.  Perhaps the first step of this effort is  
to
further discuss these and to solicit other uses from the community.
Maybe this can take place with various developers stating "for my
service to use this API, I would like it to do X."

> As far as proceeding on that front - it is probobably something that  
> needs
> to get discussed face-to-face and initially prepared by a group of  
> ppl. The
> scope of this also extends beyond the European/java-ls-api effort.

Absolutely agreed.  We should definitely put this on the agenda for
the next joint meeting.  This question is central to interoperability
and to performance and thus it probably warrants a few teleconferences
among interested parties.

best,
martin