perfsonar development work

["Jeff W. Boote" <>]

Roman Lapacz wrote:
> today I have added new message service which allows to get lookup 
> information directly from the service. It might be useful if there is no 
> available Lookup Service but the client application knows the service 
> address and wants to get more general service info.

I absolutely agree.

> This message handler is a part of pS base so all it's needed to have it 
> working is adding its name (LookupInfoRequest) to service.properties 
> file in service.ma.message_types property.

Is there some reason not to use the LSQuery message type? It is already well 
defined for the LS. If you can reuse it, then clients can reuse most of the same 
code they use to query an LS for multiple services to query the single service.

I think we should strive to reduce the number of distinct message types that are 
in use... (If there is a reason not to use it - I'm not against creating new 
needed message types. I would just like to see re-use whenever possible.)

> Now we have small lookup information set:
>
> - service access point
> - service name
> - service type
> - service description
>
> I'd like to propose to extend it. Some time ago we had the discussion 
> about this, take a look:
>  http://wiki.perfsonar.net/jra1-wiki/index.php/LS_structure
>  http://wiki.perfsonar.net/jra1-wiki/index.php/Service_properties_file
>
> For near future I'd like to propose these:
>
> - service version
> - organization/domain
> - contact email

Sounds reasonable.

jeff