perfsonar development work

[Maciej Glowiak <>]

Hi Roman, Loukik, Szymon,

> I would prefer to have the base which is very generic (for services and 
> clients; interfaces, utility classes) and does not have the 
> implementation directly connected with specific service type 
> implementation. This could be a light framework easy to understand by 
> new developers.
>
> But I see your point. Such base might need many libraries for 
> compilation but some of them would not have to be used to compile and 
> run a service Thus some of them which are useless, for example for MA, 
> would not have to be put in the installation package of MA. This 
> approach could be accepted by me.
>
> Maciej which solution you prefer?

I'd prefer something between them two. There is a question what should 
be inside base. Of course generic architecture/framework and classes 
shared between services?

What if something changes? I had such situation in LS. I need have to 
re-implement some DB functionality, but it'd interfere other services 
using StorageManagers. So I decided not to put it inside base so far, 
but the same problem will be in the future. Keeping too much 
functionality inside one base may cause the base will contain only 
(mostly) a lot old  unused classes, because new classes will be 
incompatible.

Perhaps we should consider divide base on a few jars (?) such as 
perfsonar-base-core.jar, perfsonar-base-xmldb.jar, perfsonar-base-nmwg.jar


> > I don't have a strong opinion about creating a trunk/services 
> > directory and having all services put in there. I am not in favor of 
> > it but don't oppose it either.
> > The important question however is...there will be clients which will 
> > act as services as well. Where will these fit?
>
> In SOA the service usually have both functionalities: server and client. 
> But it's still a service. You could ask will our client applications be 
> pS services (for example, perfsonarUI)? I don't think so.

I agree. Services are also clients (in networking meaning) but not in 
perfSONAR meaning. Clients are mostly visualization tools. I remember we 
defined somehow the "client" term for perfSONAR, and AFAIR it was 
something similar to my understanding.


> > - There will certainly be services which will act as both MA and MP or 
> > more (for example, MA and transformation). Where will these fit?
> > - I don't like this idea.
>
> You right. We could have just 'service' directory. Hmm, this strengthens 
> the argument to use the bundle with all base stuff (even service specific)

Agree.


> > Service naming convention - we need one. We all agreed to using one in 
> > the last january workshop. It wasn't a strict naming convention but 
> > sufficient to get enough information made available by the developers 
> > in a name.
> >
> > The development teams can still choose the names for their products 
> > but have to provide required information in the name.
> >
> > (This was already agreed in the last workshop. To avoid re-discussing 
> > the same issue again, if anybody wants to change this decision, he/she 
> > should make it clear as to why this (re-)discussion is required. I 
> > haven't seen a strong reason for not following this naming convention)
>
> As I wrote in one of my previous emails. I wasn't stuck to presented 
> names of service directories (it's up to service developers and naming 
> convention).

Yes, I remember the discussion, but was it finalized and is somewhere 
written down (on perfsonar.net)? I am not so sure.
Personally I don't like prefixes such as j- or py-.

Szymon Trocha wrote:
> Roman Lapacz wrote:
> [...]
>> Maciej which solution you prefer?
> [...]
> Let's ask what the other developers think about proposals you are
> dicussing?

Of course, I think Roman asked me because nobody else (but Loukik, Roman 
and me) has been discussing that topic so far.

Maciej

--

 --------------------------------------------------------------------
| Maciej Glowiak        Network Research and Development            ||
| 

     Poznan Supercomputing and Networking Center ||
| (+48 61) 858 2024          -- skype_id: maciej_psnc   GG: 4526858 ||
 ====================================================================