Hi,
I'm not sure if I put this question in the right forum, but here we go...
First of all I've been wondering how a THREADED variable is different from a global variable + critical sections? I've done a simple threaded test with a test-exe starting threads and there seems to be no performance loss.
But still, what other way is there?
Second, I'm mostly building for the web (using isapi extensions) so in my case I always have multi-threaded apps. But with the new version, I want to get global memory 'over' all isolated worker threads (in IIS). What I found is that - since the IIS worker threads are isolated - they do NOT share memory from the isapi (eg a DLL using global variables) between one another.
Has someone does this before or point me in right direction?
Many regards
Jeroen Brouwers
I'm not sure if I put this question in the right forum, but here we go...
First of all I've been wondering how a THREADED variable is different from a global variable + critical sections? I've done a simple threaded test with a test-exe starting threads and there seems to be no performance loss.
But still, what other way is there?
Second, I'm mostly building for the web (using isapi extensions) so in my case I always have multi-threaded apps. But with the new version, I want to get global memory 'over' all isolated worker threads (in IIS). What I found is that - since the IIS worker threads are isolated - they do NOT share memory from the isapi (eg a DLL using global variables) between one another.
Has someone does this before or point me in right direction?
Many regards
Jeroen Brouwers
Comment