Hey there. We are currently using NT 4 server, and have our communications dll registered with MTS.
This is what happens:
The client sends variables to the dll on the server regarding who they are. Based on that, their FTP directory is changedand they recieve the correct logon and password for that directory. Each account that uses our software is using a different directory, with different logons. New files on their system that pertain to our applicaton are uploaded to the server. They disconnect, then reconnect and re logon. New files on the server are downloaded to their computers. Simple.
However, we believe that because of MTS caching instances of our DLL, some accounts are recieving other account’s information. We just recently had one account recieve the upgrade to the software that was intended for another account. Now, because our software is extrememly customized to the individual account, this is causing some major concerns. It seems that the more people we have hitting the dll, the more this problem happens.
It has been suggested that we use DLLHost, but we cannot get it to work. It has also been suggested that we upgrade to Windows 2000 and use the Component Services. But, we would still need to know how to isolate each instance’s variables, and keep them from being cached and shared across accounts. Any suggestion would be seriously appreciated.
