V
Venkat Venkataramanan
Hello:
I have a UI layer that interacts with the business layer
which interacts with the DB layer.
I have developed the business layer as a class library
that complies to a DLL that will be stored on the server.
So, every client application that is launched will have
to run an instance of the DLL that will run in the
client's memory footprint. While this may potentially
scale better from the distribution of the DLLs to use the
horsepower of the client workstations, I am running into
the risk of opening one database connection for each
application.
In the days of VB6, there were Active Servers and in-
process DLLs. How can I create an Active server look-
alike under vb.Net? This was I can run one instance of
the Active Server at the server level that can use
database connection pooling to reduce the number of open
connections.
Thanks.
Venkat
I have a UI layer that interacts with the business layer
which interacts with the DB layer.
I have developed the business layer as a class library
that complies to a DLL that will be stored on the server.
So, every client application that is launched will have
to run an instance of the DLL that will run in the
client's memory footprint. While this may potentially
scale better from the distribution of the DLLs to use the
horsepower of the client workstations, I am running into
the risk of opening one database connection for each
application.
In the days of VB6, there were Active Servers and in-
process DLLs. How can I create an Active server look-
alike under vb.Net? This was I can run one instance of
the Active Server at the server level that can use
database connection pooling to reduce the number of open
connections.
Thanks.
Venkat