I had posted a while back with regards to moving our code away from MFC
ISAPI because it is no longer really supported.
I am working now with the port and have... Step 1 refactored my classes to
work as an ISAPI without the MFC layer. And then Step 2, refactored again to
expose the methods without passing in the ECB and without WriteClient
(basically string in and string out).
I am now trying to front-end the Mixed Class with a Managed ref class. And
the test harness seems to be working well, with one exception...
The duty of this particular ISAPI Extension is to manage database
connections and some session info, sort of like a proxy, or state server.
The problem I am running into is that each connection now seems to be new
with its own space, and at this point, all of the static connection
information is not available.
May I ask for a nudge in the right direction?
What I have done so far is create a Windows Service that on start,
initializes the dll so that it is up and running all of the time. And the
hope is to have the IIS module or handler connect to the dll and access the
manager to set and get info.
Thanks in advance,
Mike