Abstract
The CAAS™ (Content Aware Advanced Storage) protocol is an application protocol that defines client and server
computational behavior, mainly the ordering of operation sequences, based on contextual data analytics.

Intro:
The protocol is TCP/IP based, follows the RPC (Remote Procedure Call) model; allows the client and server to be
in different locations, as long as they have a medium to communicate over (Internet, LAN, etc).
RPC is a type of request–response protocol.
An RPC is initiated by an application on the client, sending a request message to a known remote server to execute
a specified procedure with supplied parameters.
The remote server executes the query and then sends back a response to the client, and the application continues its
process.
While the server is processing the call, the client is blocked (it waits until the server has finished processing
and answered, or times out, before resuming execution).

The CAAS protocol is unique in the sense that it is content aware, this is to say that based on the type of request,
the value of its parameters (commands and attributes) and the data made available by the CSAL™ back-end, the server’s
computational behavior and subsequent calls will vary.
CAAS enables any WarpStor client linked with the CAAS library to encode and pass commands and attributes associated
with workspace management to the WarpStor server.
These commands and attributes contain workspace content-aware data such as specific methods, workspace name,
 owner UIDs and GUIDs, workspace roles and identifiers...
The WarpStor server will decode those commands and attributes; it will then perform appropriate actions based on the
feedback of the CSAL™ layer in order to optimize operations.

For example, when a CAAS-enabled client requests a new workspace for a specific project, the Warpstor Server will
decode the workspace and project attributes; it will query CSAL (contextual Storage data analytics layer) to find out
if the creation operation can be optimized.
If CSAL™ is aware of the project ( another user might be working on it already); it will suggest that the server
executes a cheap clone function instead of an expensive creation/sync/export sequence of ops to build the new workspace.
Without CAAS, the server would have created a duplicate copy of pre-existing data. Thanks to CAAS protocol, the server
behaved more efficiently based on data provided by the client and the CSAL layer.