Hi,
Does anybody have expertice on getting a PB DLL connected to the internet?
I'm getting stuck here: I wrote a simple VB ActiveX which calls the PBDLL. It works just fine as long as you keep it to single threaded.
As soon as I compiled it in apartment threaded mode the CPU time of IIS just through the roof and crashes hard.
I already rewrote my DLL to be thread safe, that is: all variables local with one time internal threading where I pass my data from the sub that creates the threads (2 actually) using CoTaskMemAlloc. So it should be thread-safe.
I already tested it like this: a VB app uses the DLL and provides a series of imputs, expecting output. If I run the test with 2 applications, they don't interfere with oneanother. So it seems fine.
Anybody got any ideas what I'm doing wrong / have to do, to get it work from a ASP webpage using CreateObject, call function (in ActiveX).
Hope someone can help
Sincerely
Jeroen
------------------
Does anybody have expertice on getting a PB DLL connected to the internet?
I'm getting stuck here: I wrote a simple VB ActiveX which calls the PBDLL. It works just fine as long as you keep it to single threaded.
As soon as I compiled it in apartment threaded mode the CPU time of IIS just through the roof and crashes hard.
I already rewrote my DLL to be thread safe, that is: all variables local with one time internal threading where I pass my data from the sub that creates the threads (2 actually) using CoTaskMemAlloc. So it should be thread-safe.
I already tested it like this: a VB app uses the DLL and provides a series of imputs, expecting output. If I run the test with 2 applications, they don't interfere with oneanother. So it seems fine.
Anybody got any ideas what I'm doing wrong / have to do, to get it work from a ASP webpage using CreateObject, call function (in ActiveX).
Hope someone can help
Sincerely
Jeroen
------------------
Comment