• One DBManager per session of the DAQ.
• DBManager with 3 interfaces: to TableSpace, to TStore and to Adapters

• TableSpaces act as the transport from the DBManger to the Adapter level. Note: DBManager and TableSpace may be the same thing? Not from depoyment point of view?
• Interface TableSpace-Adapter: should allow TableSpace to access to all data identified by a query:

      class Query {
          string Name;
          map<string,Serializable*> Parameters;
      }
  

  Name and parameters completely specify the interface for any TStore-wrapped SQL query.

• Adapters: objects that know how to convert sets of xdata::Tables (QueryResults) into c++ high level objects. They should be able to run over a TableSpace.

• Interface Adapters - DBManager: parameters exported to the DBManager info space, soap callback bounds. Note: what link beetween SOAP Callbacks and exported parameters?

      Class MyAdapter {
       public:
           MyAdapter() {
                DBManager::bind("MyCcallBack",&MyCallback);
          }
      };
  
      MyAdapter myAdapter;
      myAdapter.exportParameters(theInfoSpace);
  
  

  * Adapters are aware of the database structure, or at least of the representation of data resulting from the tstore (i.e. the QueryResults).

-- PasqualeMusella - 10 Apr 2007