2 ActiveX process share one newlisp.dll
Posted: Fri Apr 08, 2005 1:36 pm
I ran into a new problem with the DLL.
Using it from 2 different instances of a WIN-Standard-exe gives no problem.
Both sessions have their own memory-workspace and work side by side.
Now I get a different situation. I call newLISP.dll from an ActiveX component embedded in an HTML-file running in iexplorer. Now I run a second instance of iexplorer with the same HTML-file. Now I get errors complaining about protected symbols in my initialisation files. So it seems to use the same DLL/memory workspace. I see 2 instances of iexlorer in the process list but it maybe that the ActiveX-function share the same DLL.
The only solution which came to my mind, is to make unique newLISP.dll's for each instance on the fly to avoid this conflict.
Other idea's ?
Using it from 2 different instances of a WIN-Standard-exe gives no problem.
Both sessions have their own memory-workspace and work side by side.
Now I get a different situation. I call newLISP.dll from an ActiveX component embedded in an HTML-file running in iexplorer. Now I run a second instance of iexplorer with the same HTML-file. Now I get errors complaining about protected symbols in my initialisation files. So it seems to use the same DLL/memory workspace. I see 2 instances of iexlorer in the process list but it maybe that the ActiveX-function share the same DLL.
The only solution which came to my mind, is to make unique newLISP.dll's for each instance on the fly to avoid this conflict.
Other idea's ?