Forum OpenACS Development: Re: XoTCL Request Monitor on Windows
I'm following this discussion and I also noticed that nsthread.dll does not seem to be able to load properly in my distribution.
Unfortunately in these days (till Friday) I am busy at this workshop http://www.metroaerospace.org/.
I will look into the this issue and make nsthread.dll load properly as soon as I can.
Let's try to fix that:
the TCL Thread library you are trying to load with this command:
ns_param libthread $bindir/nsthread.dll
is wrong. That is not the library you want. This is a *.dll linked by default to Naviserver
(try ro rename nsthread.dll into something else and you'll see nsd.exe won't start any longer).
The library you want, in my distribution, is:
@Frank and Gustaf
This TCL Thread library has not been built the way Gustaf mentioned, so it is not immediately loadable in Naviserver.
But, if the *.dll file is properly positioned it can be "activated" when needed with the instruction
"package require Thread"
Try for instance from within DS:
package require Thread
set tid [::thread::id]
Am I still sleeping?
As soon as possible I am going to release a new version of my distribution
where Thread 2.8.0 DLL is compiled with NS_AOLSERVER flag defined, that is equivalent to the configure option --with-naviserver
Hope it helps,
This version fixes the problem of Thread 2.8.0 which now is a loadable module and some of the problems that were observed in the Nsssl module.
Hope it helps,
the --with-naviserver flag of configure declares NS_INCLUDES, NS_LIBS and defines NS_AOLSERVER. Don't load the library with "package require Thread", unless you are are asking for troubles (with the flag the registered commands are named ns_* to replace the original NaviServer/AOLserver commands).
Just curious: who observed what problems with the nsssl module?
I did compile OpenSSL and the Nsssl module with different compilation switches.
This prevented Nsssl from being able to properly call/use OpenSSL.
Now the problem is fixed.