🚀 go-pugleaf

Hi,

Borland's database application based on the structure:
Application -> Data Access Components -> Session -> TDatabase.
The key in here is simple and clear, every data access component has a
'databasename' property, with this, a global (or user defined) TSession
object can find the relative TDatabase object for the requester.  So I
belive, the TSession object play as a bridge between data accessors and
the database connnection.

I am now interesting what would happen when the world changed from c/s
to distributed. For example, if the data access components and the
TDatabase reside in different modules (i.e. corba client and server),
can the data accessors still comunicate with the relative TDatabase?
Where the TSession object get play?

Yes, I know, Borland support MIDAS, but in the architecture, only the
data-awares get apart, and this architecture is not flexible relative to
some common solutions like corba and dcom.

Any opinion and answer would be appraticated.


Regars,

steven
woodysteven@163.com