|
Enclosed a little picture of the architecture of the system, as it
should be. Which means that this architecture is currently
not used.
New: Explanations:
- The conduit framework creates and manages the connection
to the pilot, it also uses the pilot-link functionality to
query the pilot for databases in need of synchronisation.
- To that end it also creates the appropriate database object,
which then calls the conduit database through some hooks
mechanism. That one then searches for an appropriate conduit and
configures the db object to use that for data conversion (and
maybe as target for the converted information, the conduit would
have to have storage capabilities then too).
- To accomplish the described actions the existing conduits
have to register themselves at the conduit database, and that one
has to register itself at the hook mechanism.
New: Using an OO approach results in a simpler
system:
|
