| Subject | Re: [IBO] What connection component should I use |
|---|---|
| Author | Pelle F. S. Liljendal |
| Post date | 2003-11-06T11:19:06Z |
In fact I am already doing "multiple transactions". On my DataModule
I (currently) have a TIBODatabase "connected with" a
TIBOTransaction, however I don't "use this transaction" (the only
reason for this transaction is I thought it "had to be there"). On
all of my forms (and runtime aswell) I placed a separat
TIBOTransaction that I used with the dataware components on that
particular form (or that particular data-manipulating-function). I
therefor guess it will be very easy for me to switch to
IB_Connection and IB_Transaction.
No doubt I will make use of several transactions, however I am not
sure if I will be using more than one connection (unless there are
some benefits of doing so ?). Prior to FB 1.5 connection times can
be "slow", especially if FB is installed on a XP machine (the case
when I "develop at home"). Hence I prefer one connection, which will
stay open during the programs duration.
Pelle
I (currently) have a TIBODatabase "connected with" a
TIBOTransaction, however I don't "use this transaction" (the only
reason for this transaction is I thought it "had to be there"). On
all of my forms (and runtime aswell) I placed a separat
TIBOTransaction that I used with the dataware components on that
particular form (or that particular data-manipulating-function). I
therefor guess it will be very easy for me to switch to
IB_Connection and IB_Transaction.
No doubt I will make use of several transactions, however I am not
sure if I will be using more than one connection (unless there are
some benefits of doing so ?). Prior to FB 1.5 connection times can
be "slow", especially if FB is installed on a XP machine (the case
when I "develop at home"). Hence I prefer one connection, which will
stay open during the programs duration.
Pelle
> It depends. TIBODatabase is fine for hybrid applications such asyou are
> doing. It is a TIB_Connection descendant and the non-bufferedTIB_
> components are quite at home with it.transactions, and
>
> TIBODatabase mimics the VCL model of one transaction/one
> connection. However, the TIB_Connection handles multiple
> the TIB_Transaction handles multiple connections. UnlikeTDatabase,
> TIBODatabase *can* take additional transactions (that's what thetransactions, it
> TIBOTransaction component is for), though (IMO) it is messy.
>
> If/when you get into multiple connections and multiple
> will simplify your application architecture to use separateTIB_Connection
> and TIB_Transaction components instead of the compositeto
> connection/transaction component. Your TIBO* datasets can connect
> TIB_Connection via the IB_Connection property and you can managetheir
> transaction side explicitly, via the IB_Transaction property.model so
>
> I'm figuring that you are clicking onto the power of the non-BDE
> fast that it won't be long before you start looking into thebenefits of
> multiple transactions.
>
> Helen