Best Multi-user design technique using MIDAS?
Rafey
I wanted to find out what are the Best multi-user techniques and their
Consequence in MIDAS. I am here in good deal of confusion about multi-user
issues using MIDAS. I need your immidiate attention. Please help. Here are
couple techniques which I could think of right now but both of them are not
satisfactory:
1- Set Instancing property of App-Server = SingleUse. In this way every
client would be associated to a single instance of App-Server. For example
if there are 3 clients then 3 App-Servers will be instantiated.
2- Set Instancing property of App-Server = MultiUse but have two or more
Session components on Remote Data Module. In this way some Database
and consequently Provider (or TQuery, TTable) components will be attached
to different TSession. For example, suppose there is a Remote Data Module
with following configuration:
- 2 TDatabase components. Database1 & Database2.
- 2 TSession components. Session1 & Session2.
- 10 TQuery components. Query1 to Query10 ( 5 attached to Database1 and
remaning to Database2).
- 10 TProvider components one for each TQuery. Provider1 to Provider10.
You can well imagine that there are now two channels
available to send queries to Database. Single instance of App-Server is used
to fullfill all user requests.
I can't think of any other multi-user design using MIDAS. What are the other
possibilities to develop a multiuser application using Delphi/Sybase/MIDAS.
Please advice. Thanks for your help in advance.
Rafey.
eng...@yahoo.com