 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
Volume
|
|
 |
|
|
|
|
|
|
– |
Many domains (in
Grid, systems management) have lots of
|
|
|
attributes
|
|
|
|
– |
GetXXX/SetXXX
becomes unwieldy
|
|
|
|
Explode
WSDL
|
|
|
 |
|
|
|
|
|
|
Explode
size of client proxy
|
|
|
 |
|
|
|
|
|
|
– |
More difficult
to detect the pattern across all operations and then
|
|
derive the
attribute set
|
|
|
|
Just
use Get(xxx) and Set(xxx)
|
|
 |
|
|
|
|
|
|
– |
But how does the
Requestor reason about which xxx are valid?
|
|
|
|
Avoid
situation of inheriting unwanted access
|
|
 |
|
|
|
|
|
operations
|
|