🚀 go-pugleaf

Hello all,
In my company, we developed  a web site accessing a mainframe. We used IIS4
and ASP pages calling COM objects ( responsible of connection, exchange and
disconnection with mainframe) . The COM object responsible of connection and
disconnection is a DLL COM and is "instantiated" with CreateObject each time
an asp session is created. This COM object also instantiates a not COM
object,in fact, a classical DLL performing the tcp/ip connection to a
gateway. We found that we had only one instance of this classical DLL.
A problem arises when one ASP session is ended :

The COM object responsible of connection and disconnection is decremented
his usage counter and stays in memory but the classical DLL is demapped
from memory after several minutes (till 5) unless others asp sessions are
still living.

Can anyone help me in this mix of DLL COM and classical DLL?
Can a classical DLL be loaded from a COM DLL ? It's my main question.
Is there a problem of keeping in memory classical DLL when loaded by COM
objects?

John Gosset
Communication System Engineer
john.gosset@ag.be (at my office)
john.gosset@village.uunet.be (at home)