RE: AW: [geclipse-dev] Storage vs. Service

["Ken Meacham" <kem@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Hi Mathias, Ariel, etc,

> > i never understood why IGridJob
> > is an IGridResource... i am missing something for sure).
> 
> The original meaning of IGridResource was that Grid resources 
> are non-local entities. Since a job is running on the Grid it 
> is non-local. I know, it does not make too much sense and I 
> personally have no string opinion on making it a Grid resource or not.

This does actually make sense to us! In GRIA, we refer to "resources",
which are created and managed at a service. These resources could be,
e.g.:
- data stager (at a Data Service)
- job (at a Job Service)
- SLA (at an SLA Service)
- registry (at the Registry Service)

Each resource has a type, defined in its endpoint metadata, so the
client GUI (via service-specific plugins) can determine how to represent
them in the resource tree, or provide specific display panels, etc.

So the definition of an IGridResource as "an object that is created and
managed by a Grid service" seems fine. Of course you might argue that a
user creates a data stager, for example, but actually this is just a
request to the service to create an object on its site, which is then
set to be "owned" by that user. The user interacts with this resource
via a reference to the remote object. 

Hope that helps,

Ken.