perfsonar development work

[Jason Zurawski <>]

Maciej;

> > > > What do you mean by this, no muliple parameters and instead just 
> > > > have multiple eventTypes (I would prefer it that way, the only 
> > > > reason I stick in supportedEventTypes is for legacy client and 
> > > > servers).
> > >
> > > Jason,
> > >
> > > I meant that soon we'll be migrating (re-writting much code) to 
> > > perfSONAR base-2 which is under development but Roman is now working 
> > > on moving RRD MA to it. We may easily implement there such 
> > > improvements as multiple parameters or multiple eventTypes if 
> > > necessary.
> > >
> > > For existing services based on current perfSONAR base and current 
> > > NMWG implementation it would be more difficult and time consuming, 
> > > so in my opinion it we should not make an effort to implementing 
> > > those features in current base/nmwg.
> >
> >
> > Please note that the in general the gLS (in particular the 
> > perfSONAR-PS beta) should and will continue to support the 
> > multiples.  There is no other way to complete both the summarization 
> > registration or discovery messages without this notion.  With your 
> > implementation not doing this, it will make interoperability very 
> > difficult (impossible in the case of synchronization between gLS 
> > instances).  I do hope that you and Roman can resolve this issue 
> > quickly.
> I think we won't be able to do it until the Berlin meeting. I'll be 
> updating NMWG classes tomorrow (introducing new namespaces - are they 
> already final?), so I will take a look on that.


Nothing is ever final :), but the two that I have mentioned are what I 
am using.

-jason