Warning:
JavaScript is turned OFF. None of the links on this page will work until it is reactivated.
If you need help turning JavaScript On, click here.
The Concept Map you are trying to access has information related to:
Chapter 8 Trans, The design must balance the flexibility and scalability that derive form transparency against software complexity and performance. Scaling Transparency The service can be expanded by incremental growth to deal with a wide range of loads and network sizes, The design must balance the flexibility and scalability that derive form transparency against software complexity and performance. Performance Transparency Client programs should continue to perform satisfactorily while the load on the service aries within a specified range., The design must balance the flexibility and scalability that derive form transparency against software complexity and performance. Access Transparency Clent programs should be unaware of the distribution of files. A single set of operations is provided for access remote files without modification, The design must balance the flexibility and scalability that derive form transparency against software complexity and performance. Mobility Transparency Neither client programs nor system administration tables in client nodes need to be changed when files are moved. This allows file mobility-files or, more commonly, sets or volumes of files may be moved, either by system administrators or automatically., File System Requirements: Transparency The design must balance the flexibility and scalability that derive form transparency against software complexity and performance., The design must balance the flexibility and scalability that derive form transparency against software complexity and performance. Location Transparency Client propgrams should see a uniform file name space. Files or groups of files may be relocated without changing their pathnames, and user programs see the same name space wherever they are executed.