🚀 go-pugleaf

Hi Mark,

May be I described our situation unclear.

We are using DCOM in Apartment threading model running as Remote AppServer,
from client side we have just normal application connected to AppServer
through
TDCOMConnection and uses TClientDataSets. Our sever has one RDM which
contains one shared DB object,
one TSession object with AutoSessionName, many TQueries, TUpdateObjects and
TDataSetProviders,
multithreading.

As we figured out, AppServer allows to have only 256 clients connected
because BDE treated AppServer in DCOM implementation like one client app
 on that machine ),
and all the threads created inside AppServer ignored by BDE as new client
connections
and BDE allows to have in this case only 256 sessions open for whole
AppServer.
But we actually must to support more simultaneous connections.

What's wrong in our schema?

Dmitri


"Mark Cashman" <mcashman@temporaldoorway.com> wrote in message
news:3AE0EC41.F72DDAE9@temporaldoorway.com...
> I find it hard to imagine the computer on which you are running is large
> enough to sustain that level of concurrency, even under NT.
>
> Why do you need 256 threads per client?
>
> ------
> Mark Cashman (TeamB - C++ Builder), creator of The Temporal Doorway at
> http://www.temporaldoorway.com
> - Original digital art, writing, music and more -
> C++ Builder / JBuilder Tips and The C++ Builder Programmer's Webring
> (Join us!)
> http://www.temporaldoorway.com/programming/index.htm
> ------
>
>