perfsonar development work

[Szymon Trocha <>]

Jeff W. Boote wrote:

[...]
> > If I remember correctly we were working in Poznan mainly on 
> > SetupDataRequest-FilterRRDSelect-2.xml and 
> > SetupDataResponse-FilterRRDSelect-2.xml. I don't think we removed any 
> > message examples from CVS.
>
> Yes, this is the example I was looking for. In the 'select' metadata 
> there is 'resolution'. It was my understanding that this was intended to 

I guess these are the examples you were looking for:
http://wiki.perfsonar.net/jra1-wiki/index.php/Setup_Data_Request_with_metadata_and_filtering
http://wiki.perfsonar.net/jra1-wiki/index.php/Setup_Data_Response_with_metadata_and_filtering

> map to 'step' in an rrd. I believe the problem is really on the side 
> that the client can not easily find out the 'available' resolutions. If 
> the client requests a resolution that is not available, it could return 
> an error response.*
>
> It is my opinion that services should not be computing derived 
> resolution datasets on the fly - they should serve what they have. If we 
> want a service to compute derived datasets - the 'transformation' should 
> be described (and requested). Note: I'm not saying that it could not be 
> implemented as part of the same service, just that this type of 
> transformation should be represented by the metadata chaining. So, it is 
> clear when derived data is being used - and when more direct data is 
> being used.

Didn't we envisage the transformation service for such purposes like 
data aggregation?

Regards,
--
Szymon Trocha

Poznan Supercomputing & Ntw. Center ::: NETWORK OPERATION CENTER
Tel. (+48 61) 8582022
http://noc.man.poznan.pl  ::: http://noc.pionier.gov.pl