perfsonar-dev - Re: [pS-dev] one base vs. two bases (svn structure)
Subject: perfsonar development work
List archive
- From: Loukik Kudarimoti <>
- To: "Jeff W. Boote" <>
- Cc: Roman Lapacz <>, "" <>
- Subject: Re: [pS-dev] one base vs. two bases (svn structure)
- Date: Tue, 12 Jun 2007 15:56:04 +0100
Jeff W. Boote wrote:
Roman Lapacz wrote:
Hi,
during the last meeting in Cambridge (GN2 workshop) we decided to have two base products in SVN structure: one for client and one for services. Today I came back to this and started analyzing the sources. I came to conclusion that we have some classes that can be used either in clients or services so there was a problem which base I should use (we must remember that our structure must be clear and logical to new developers).
The proposal was:
client-base : Anything that is needed by both clients and services
service-base : Anything that is ONLY needed by services
The point was to make the client jar as small as it could be since it will be used by many applications. But, to provide all the functionality required to write a client application.
If this split is not useful now that you are really looking at the code while considering it, then of course it should not be done. I am fine with either solution. I just responded because it is clear where the code you are referring to should be placed (client-base) if the split is done.
If I understood Roman correctly, I think he wasn't sure where to put code that *we think* can be used by clients as well. But such ode is only used by services at the moment. If we think along those lines, a large part of the code base would actually end up on the client side.
jeff
- one base vs. two bases (svn structure), Roman Lapacz, 06/12/2007
- Re: [pS-dev] one base vs. two bases (svn structure), Jeff W. Boote, 06/12/2007
- Re: [pS-dev] one base vs. two bases (svn structure), Loukik Kudarimoti, 06/12/2007
- Re: [pS-dev] one base vs. two bases (svn structure), Jeff W. Boote, 06/12/2007
Archive powered by MHonArc 2.6.16.