For every globus-url-copy call, the globus-url-copy client should send the following information to a centralized MDS. The information should include
a) For a two-party transfer, the client url, server url, file size, time
taken to transfer
b) For a three-party transfer, the source server url, the destination
server url, file size, time taken to transfer

Every subsequent globus-url-copy should be able to then access this MDS
and perform some informed decisions.

To do this, I am trying to write a ExternalElementProducer
Information provider. This requires specifying the location of a script
in the file rp-provider-config.xml and to specify the periodicity with
which it will run and populate MDS. However, for my purpose,
a globus-url-copy call should send the data to MDS as and when it is
called. So, this is more like an on-demand push based data publishing
model instead of a pull based model which seems to be used when a script
runs periodically and MDS gets the
data from it.

Essentially what I need  is some C API which when used within
globus-url-copy, would transfer or push the above mentioned data to the
MDS. Is it possible to do that in Globus ?

it seems to me that you could do this by scripting around globus-url-copy and using the existing mds and ws utilities in the toolkit.

Reply via email to