IIRC, IIS does some cacheing of its own to help performance. I agree that a managed pool is the best approach, but the overhead of creating/releasing objects may not be all that bad. VFP MTDLL's were built with this scenario in mind. It's certainly not completely loading/unloading the entire VFP runtime with every call. Rick and Christof W. have written articles on the subject, and there's also info in the documentation about how it works.

>Hi, hopefully someone can get me some direction on this... How / what ways are there of creating a pool of COM servers at the global application level to be used within a .net project... Like that of West-Wind Web Connection, where there can be many loaded, then as requests come in, it gets assigned to one request at a time, does the work, then returns as active to the pool. Obviously, the benefit of not having to keep re-creating / releasing on every request.
>
>I have an app going, but each location where I need to make a call, I am issueing a
>
>dim MyObj as VFP_COM.COMClass = new VFP_COM.COMClass
>
>sometimes, it fails creating at different times while servicing a single request... I'm sure there are more efficient ways, but am puzzled...
>
>TIA...