Cloud Data Management Interface: Difference between revisions

Revision as of 14:12, 24 July 2020

Revision as of 17:59, 21 November 2020

Line 20:

==Capabilities==

Compliant implementations must provide access to a set of configuration parameters known as ''capabilities''.

These are either boolean values that represent whether or not a system supports things such as queues, export via other protocols, path-based storage and so on, or numeric values expressing system limits, such as how much metadata may be placed on an object. As a minimal compliant implementation can be quite small, with few features, clients need to check the cloud storage system for a capability before attempting to use the functionality it represents. Resource allocation assignments limited to the data management interface protocols must possess access bypass capabilities which extend beyond the layered framework.<ref>{{cite book |last1=Metheny |first1=M |title=Federal Cloud Computing: The Definitive Guide for Cloud Service Providers |date=2017 |publisher=Syngress |pages=202-245202–245}}</ref> This integral function is vital to the prevention of transport layer session hijacking by unauthorized entities which may circumvent standard interfacing security parameters.<ref>{{cite book |last1=da Fonseca |first1=N |title=Cloud Services, Networking, and Management |date=2015 |publisher=John Wiley & Sons |pages=70-9870–98}}</ref>

==Containers==