>>
>>
>>Which is why VFP works best with multiple In-Process exes on SMP CPUs - If I remember correctly Rick Stahl recommended a max of four CPU per box, each running its own In-Process app.
>
>
>Can you clarify this? There is no such thing as an in-process EXE.

Opps! Typo!... I should have typed 'dll'.

Here's what Rick said,
"Apartment Model threading also makes it possible to run VFP components inside of Microsoft Transaction Server. Unfortunately, the blocking issues also affect the way VFP components run inside of MTS. Just as with objects called directly from a client, the issue is now migrated to the package level – instead of IIS being the client process now an MTS Package becomes the host object. The same problems arise as the same object in a package cannot be accessed simultaneously due to the problems with the VFP runtime blocking. Concurrent method calls can only be achieved by objects hosted in multiple separate MTS packages. With MTS this blocking issue is even more pronounced than with directly accessed objects as all object access on the machine is routed through the MTS package. This means that multiple client processes (say the IIS Process and a VFP application both using this object on a server) now have to fight for contention.
.....Web Connection and FoxISAPI include a built-in pool manager that allows managing multiple object references and handing these references to clients as needed. If one instance is busy another reference is handed off – if all instances are busy requests are queued and serviced when a pool reference becomes available. These components run best as Single Use Out of Process EXE servers and allow for immediate deployment on local and remote machines via DCOM. While Out of Process components are slightly slower (in this scenario), call overhead is measured in fractional milliseconds per Web request. EXE servers also afford better stability, process isolation that won't crash the client (IIS) on an error, and a configurable security environment.

Currently, this model provides the best scalability you can achieve with VFP COM objects – at Surplus over 50 servers run and service a single application."



The point I was trying to make in my poor way was that Rick felt it necessary to write 'wc.dll' to achieve the results he was seeking.
His WebConnection Framework takes most of the work out of setting up a website using VFP. In addition to VFP (*.dbf's) we also use Oracle but were concerned about the costs with Oracle's new licensing model. I was asked to research other tools and backends that were more affordable. I looked at Cold Fusion, InderDev, PostgreSQL, MySQL, PHP4, Python, iHTML and other front and back ends.
We decided that we already use dbf's so why not use something that encorporates dbfs seamlessly. That brought us down to two tools: InterDev and WebConnection. With West-Wind actual VFP code (using ltc% %rtc tags) could be embedded in scripts, templates and HTMLs, and the actual serverside code can be VFP programs, it became a no-brainer choice. Very nice tool!