DIRACGrid/DIRAC — Issue #362: RSS Clients naming convention
Author: ubeda
Created: 2011-12-06 10:27:20+00:00
State: open

Hi,

triggered by this issue https://github.com/DIRACGrid/DIRACWeb/issues/43 and also comment of Andrei on BiLD - 6/XII/2011,
here we go:

having understood how RSS works ( at least the ontology, see here ~ubeda/public/html/AdministratorGuide/Systems/ResourceStatus/index.html ) and how the Client looks like ( see here ~ubeda/public/html/CodeDocumentation/Systems/ResourceStatus/Client/index.html ) we can start this issue.

RSS uses the following conventions:
- insert
- update
- get ( btw, should be moved to select instead )
- delete

which correspond with the SQL statements primitives. Basically, them provide "direct" access to the DB without much trouble.
There are other methods such as:
- addOrModify
- other methods less generic ( outside RSS, but quite used inside )
- functions I want to get rid of: a.k.a ResourceStatusClient.getMonitoredsStatusWeb among others

It has been implemented thinking on writting as general and simple functions as possible. We got rid of particularizations, external modules, we try to follow a "strong" naming convention, etc..

This is a design issue, and there is no good or bad solution, only understood and agreed solution.

Talk now, or don't complain in the future.