perfsonar development work

[Jeff Boote <>]

Andreas,

Just wanted to point out that our circuit-status service (E2EMon  
compatible) is a transformation service. It takes requests in the  
E2EMon style, and contacts two independent services (a topology  
service and a link-status service) to handle the request.

I bring this up because it may represent a slightly different Use  
Case model than you have. (It is somewhat similar to UC5/6, but in  
our case the circuit-status service polls the other services to  
determine what it can register to the LS.)

jeff

On Mar 5, 2008, at 6:04 AM, Andreas Hanemann wrote:

> Hi all,
>
> In attachment I am providing a document about the Transformation  
> Service. It contains a discussion about the scope of the service  
> and also a description how the protocol for the service may look  
> like. Some comments are left in the document which result from  
> discussions involving few JRA1 people (Nina, Szymon and Nicolas).
>
> Comments especially for the scope and the protocol would be desired.
>
> Best regards
> Andreas
>
>
> <Transformation-Service_v4.doc>

--
Jeff Boote