>I was wondering if there might be a way to calculate load densities and capacities for a VFP MTDLL? How can a maximum capacity for a VFP MTDLL be determined? What kind of design remedies are available should the pool "flood"?

Well that's the problem with MTDLL. You as the client application have no control over it because the host (IIS) is not under your control and you can't even unload yourself.

>There are internal SYS calls (2336) that can help queue the pool. Is this necessary for a MTDLL?

SYS(2336) provides Critical section support which is a BLOCKING feature for thread synchronization. This only allows you to block code from running while in the critical section.

>I saw (and tried to bibliograph) something I read regarding WC interoperability with VFP COMS MTDLLs (and even foxISAPI). Did I misread?

No, Web Connection has an option to run using MTDLLs inside of ASP. But I don't recommend it for a number of reasons. You're basically giving up all the management features and performance benefits that Web Connection provides. It's like a downgrade loosing features and performance, so obviously we don't recommend it. But this is a very specific scenario with Web Connection code which is not 100% optimized for MTDLL operation.

Over the weekend I wrote up a BLOG entry comparing Web Connection and classic ASP + MTDLL COM.

http://west-wind.com/weblog/posts/1475.aspx

We've been over all those on this thread, but this post backs up some of the things I've been talking about with numbers and more detailed explanations.