perfsonar development work

["Jeff W. Boote" <>]

 wrote:
> Hi all,
>
> Are there any interfaces/implementations that provide inter-services  
> communication? Currently we make our CLMP store responses locally and  a 
> perl script sends them to a SQL MA for DB storage. The CLMP should  send 
> the store request directly, has this been considered already?

Did you have in mind that the client request would indicate where to store the 
data? Or that it would go to a specific MA as part of administrator configuration?

We did have in mind that 'data handles' would be used for this type of 
interaction. See Push and Pull in the Vocabulary section of the wiki. It 
actually shows more complex models than you are probably thinking because it 
also includes the possibility of a transformation service.

Basically - the client should be able to do 3 things:
        1) Have the data in-lined in the response. This is how all services
        currently work.

        2) Request that the service create a data-handle (like a listening
        socket*). The service would then return a handle to the client which
        would tell the client how to get the data. (This can be thought of as 
a
        sockaddr(IP/port) to use with connect*)

        3) Specify a data-handle that the service should send the data
        results to. In this case the client will have already created a
        listening socket - and the service will send the data using
        connect.

It would be possible to set this same thing up administratively. Basically 
create an MA that you administratively tell to listen for updates of a specific 
set of data. From that you would have to create a 'handle' that indicates the 
address of where the MA is listening for those updates. Then, you could 
administratively add that address into the MP as a 'handle' to send results to. 
(I've thought of doing something like this so that clients still get all 
results, but have this setup to archive all test results as well.)

* I only use connect/listen semantics to indicate the flow of information and
more specifically the initiation of communication. (push vs. pull)

jeff