Jim Starkey wrote:

> We've traditionally called it mega-database manager. The right way to
> implement it is as a separate provider under Y-valve / dispatch module l
> looping back through the Y-valve / dispatch module to access target
> databases. This allows it to access local, remote, and external
> databases through gateways.

This dramatically reduces possible optimizations for local ones, which
IMO is the more common case.


Adriano