Schema for DTN2 External Data Store client-to-server IPC requests Request the data store enumerate its capabilities: pair, field, or advanced; what languages supported (if any), etc. The data store's capabilities: pair, field, or advanced; what languages supported (if any), etc. Create a named data store Create a named data store Delete a named data storeDurableTableImpl ** Delete a named data store Open a named data store. Optionally specify a lease (in seconds), username, and password. Return a handle for an opened data store. Get status information for the open data store (list of tables) Get status information for the open data store (list of table info) Close a data store Close a data store Create a named table. Create a named table. Delete a named table and all of its elements. Delete a named table and all of its elements. Request status of a table -- schema, number of elements. Request status of a table -- schema, number of elements. Retrieve the keys for this table from the data store Retrieve the keys for this table from the data store Insert a row (multi-field element) Put (insert, add) an element into the data store Retrieve an element from the data store Retrieve an element from the data store Delete an element from the data store Delete an element from the data store Select a group of elements based on field values, return the requested fields. If no 'get's are included, retrieve all fields. Select a group of elements based on field values, return the requested fields. If no 'get's are included, retrieve all fields. eval messages have an unstructured content, and language attributes eval messages have an unstructured content, and language attributes trigger messages have an unstructured content, and language attributes trigger messages have an unstructured content, and language attributes