|
<< Click to Display Table of Contents >> Navigation: Telegram > 2020 > 05 > 18 > Telegram_2020-05-18T14 |
2020-05-18T14:53:38
There is no option
2020-05-18T14:53:47
You don't have to make a decision
2020-05-18T14:54:15
ALL data access components (Connection, Transaction, Query, StoredProc, etc) — go on the Pooled DataModule
2020-05-18T14:54:33
The UserSession is as smooth as a baby's bum after bathtime
2020-05-18T14:55:12
I like the way you have put it; many thanks
2020-05-18T14:55:48
The ServerController — at least when the App is brand new — has only one component — the TIWDataModulePool
2020-05-18T14:56:17
For me — I set the PoolCount to 5, and the GrowToSize to 100
2020-05-18T14:57:00
By setting it to 5 — the app starts up quickly — and assuming that you connect to the database in OnCreate of the Pooled DataModule — this code will run 5 times at startup
2020-05-18T14:57:56
Do you set it in codes (PoolCount) inside DataModule and where about; OnCreate event?
2020-05-18T14:58:14
So, if you have 5 sessions, and each has a Pooled DataModule locked — and then a sixth session requests to lock a datamodule — the Pool will create a 6th datamodule and keep it in memory for you
2020-05-18T14:58:44
No, I just set it manually in the Object Inspector (it's a non-visual component that sits on the visual part of the ServerController)
2020-05-18T14:59:01
Ok I see
2020-05-18T14:59:02
of course you can read the settings from a config file and set them in code, if you wish
2020-05-18T14:59:21
No no use
2020-05-18T14:59:26
Thanks
2020-05-18T14:59:46
Wanted to say no need