>Apartment model threading is not true multithreading. You're kidding yourself if you think it is.
>

They are not the same - but Claude's basic point is correct Craig. How is your response and comment germane to Claude's very cogent and lucid post?


The basic problem with pre sp 3 of VFP is that all calls to a VFP COM Component on a machine were serialized through one thread - which effectively made VFP COM Components on the web a moot point. I knew of the problem all too well because I was one of the first people who saw this problem and screamed out loud about MS fixing the problem.

So indeed - when it comes to multi-threading - what really matters to VFP developers - and this by the way is Claude's basic point - is that concurrent calls from different clients are not serialized (blocked).

< JVP >




>
>>The basic fact is that, with .vfp. mtdlls, you can have multiple threads of .vfp operating concurrently without serialization, so no threads are waiting around for another one to process. This is what most people are looking for with multi-threading in VFP (but, would like to do it in the .EXE itself). VFP mtdlls multi-thread great from a multi-threaded client like IIS or C++.
>>Yes, with the newer "Free-threading" available in C++/C#, there are less limitations to threading but also much more danger and probably over-kill for .vfp. apps...