perfsonar development work

[ulisses <>]

Hi Maciej!

On 2006-07-28 14:11:58, Maciej Glowiak wrote:
[...]
> >                   <nmwgt:direction>in</nmwgt:direction>
> >                   <nmwgt:capacity>10000000000</nmwgt:capacity>
> >               </nmwgt:interface>
> >           </perfsonar:subject>
> >           <nmwg:eventType>utilisation</nmwg:eventType>
> >       </nmwg:metadata>
> >
> >
> >  If yes, I don't understand the need for such fields
> 
> Yes, they're required. Why? Because of the schema and NMWG. Please ask 
> Martin or Jason for details.

ok, I'm curious about the direction attribute

> >  Also, if the register message doesn't contain [1], maybe there is not a 
> >  lot of advantage having a separate keepalive message. Currently I 
> >  periodically re-register.
> >  Is this wrong? Probaly I should use a sepparate the keepalive the 
> >  message, isn't it?
> 
> Now the registration component is very simple, just re-register data. 
> But if you have a lot of data, you may just send keepalive message and 
> LS will know that lookup information shouldn't be removed.

Ok, so...

[...]
> Right, keepalive contains lsKey given back after registration. The key 
> is accessPoint, because Lookup Service works in such way, but it might 
> be anything else. So - lsKey, not accessPoint.
> 
> So the idea is:
> 
> 1. You register to LS
> 2. LS gives you back a KEY
> 3.
>    a. if no changes in your local lookup info -> send KEY to LS
>    or
>    b. if there are some changes -> re-register data

     So, according to what you said :-) ...

     I would say for b: 

     if there are some changes or the registration is as simple as a 
     keepalive: re-register the data


Thanks for your explanations

        Ulisses


> 4. go to 3.
> 
> 
> >- also maybe you should update the page 
> >http://wiki.perfsonar.net/jra1-wiki/index.php/Lookup_Service_Protocols
> >  when you say "Hierarchy of result and error codes, and their 
> >  implementation, are still the subject of discussion."
> >
> >  and instead put a reference to ls.success.registration and update the 
> >  eventType in the example XML response?
> >
> >  http://wiki.perfsonar.net/jra1-wiki/index.php/Example_LSRegister_Response
> >
> 
> Yes, thanks, it should be updated. i'll keep it in mind.
> 
> Maciej
> 
> -- 
> 
>  --------------------------------------------------------------------
> | Maciej Glowiak        Network Research and Development            ||
> | 
> 
>      Poznan Supercomputing and Networking Center ||
> | (+48 61) 858 2024     http://monstera.man.poznan.pl/              ||
>  ====================================================================
>