Difference between revisions of "Talk:Multiple Domains"
Jump to navigation
Jump to search
(New page: The addition of Organization Domains into this architecture does not seem to be correct. Agent Domains provide CPU resources to power agents, and Region Domains provide CPU and storage re...) |
|||
| Line 1: | Line 1: | ||
The addition of Organization Domains into this architecture does not seem to be correct. Agent Domains provide CPU resources to power agents, and Region Domains provide CPU and storage resources to power regions. In other words, Domains are resource pools, and could quite correctly be termed "Resource Domains". | * The addition of Organization Domains into this architecture does not seem to be correct. Agent Domains provide CPU resources to power agents, and Region Domains provide CPU and storage resources to power regions. In other words, Domains are resource pools, and could quite correctly be termed "Resource Domains". | ||
In contrast, an "Organization Domain" is a type of "Authority Domain" and has nothing to do with object resourcing. If the architecture were multilayered then there would be room for an Organization Domain as a superdomain enclosing its own controlled Agent and Region domains, but in a single-tier architecture the Organization Domain shouldn't appear in this picture. It's orthogonal to Agent and Region domains. --[[User:Morgaine Dinova|Morgaine Dinova]] 04:44, 24 September 2007 (PDT) | :In contrast, an "Organization Domain" is a type of "Authority Domain" and has nothing to do with object resourcing. If the architecture were multilayered then there would be room for an Organization Domain as a superdomain enclosing its own controlled Agent and Region domains, but in a single-tier architecture the Organization Domain shouldn't appear in this picture. It's orthogonal to Agent and Region domains. --[[User:Morgaine Dinova|Morgaine Dinova]] 04:44, 24 September 2007 (PDT) | ||
* To put it another way, Organization is an attribute that applies to resource domains like Agent and Region. --[[User:Morgaine Dinova|Morgaine Dinova]] 05:20, 25 September 2007 (PDT) | |||
Revision as of 04:20, 25 September 2007
- The addition of Organization Domains into this architecture does not seem to be correct. Agent Domains provide CPU resources to power agents, and Region Domains provide CPU and storage resources to power regions. In other words, Domains are resource pools, and could quite correctly be termed "Resource Domains".
- In contrast, an "Organization Domain" is a type of "Authority Domain" and has nothing to do with object resourcing. If the architecture were multilayered then there would be room for an Organization Domain as a superdomain enclosing its own controlled Agent and Region domains, but in a single-tier architecture the Organization Domain shouldn't appear in this picture. It's orthogonal to Agent and Region domains. --Morgaine Dinova 04:44, 24 September 2007 (PDT)
- To put it another way, Organization is an attribute that applies to resource domains like Agent and Region. --Morgaine Dinova 05:20, 25 September 2007 (PDT)