[
Lists Home |
Date Index |
Thread Index
]
Another perspective might be interesting to some folks...
In Water, we attempted to generalize the concept of a
"resource" to cover local variables as well as remote resources.
We also took some concepts from the Capability Security Model.
We describe an "identifier" as a name for a resource. An identifier
is just data, and does not represent the permissions to use a
resource.
A URI is a type of identifier, and so is an expression that represents
a local variable or field.
A "resource" represents the permission (rights and capability) to
use that service/resource. A resource can be created from a base
resource and an identifier. A resource typically accesses some
local or remote resource.
I think this is a different meaning on what
others are calling a resource because it focuses on the local
handle, not the remote resource.
This is probably closer to the notion of a "resource" in programming
languages, where you might have a file "resource" which is an
open file handle. A database connection might also be considered
a "resource".
A "resource" is something that can be used.
_Mike Plusch
|
