Thanks.

Could my foxISAPI COM do the housekeeping related to CoCreateInstance issues? Is the overhead required to create references to IIS/OS registry maintenance medthods asking a bit much for a little foxISAPI COM?

foxISAPI "parks" the formvars in an INI. Suspiciously similar to CGI. Maybe all IIS services do it - I [just] pretend the client / server data exchanges are strings. I remember working an XML reciept in a foxISAPI COM and used the "loadXML()" method (merge from string), and it worked.

I guess foxISAPI or IIS just feel better assembling the packets in a disk file. Do they need to? IF they don't, can I turn it off? It's like vCard - a pain - let's make more work for ouselves:)

Is there anything I can do to my COM's VBR, the foxISAPI.INI - or to the foxISAPI.c to improve the performace (86 the INI disk writes and turning off requests to "unneeded" services)?

I have looked for info related to "tunining" the foxISAPI.INI file - but it is sparse - i confess I don't know anything about INI's:-). Packaged (foxISAPI.ini) or temporary (FOX123.INI) or otherwise!

I thought that stuff went out with W95!

>As long as you're not using the same COM object Web Connection isn't going to care about anything else running on the same machine. Nor would FoxISAPI. Both are routing through separate ISAPI extensions.
>
>One thing that could be a problem is that FoxISAPI is doing CoCreateInstance calls and not cleaning them up. Actually, Web Connection used to do that as well, but more recently Web Connection no longer makes CoCreateInstance calls in IIS as IIS already has the COM runtimes loaded.
>
>However, that issue wouldn't cause crashes, but it could result in servers that won't unload.
>
>+++ Rick ---
>
>>A few months back I was attempting to setup a foxISAPI project on a laptop. The laptop had WWC and some "docking" services for plugging into the office server.
>>
>>There were "Cocreateinstance" errors driving the foxISAPI COM, but, foxISAPI would respond to a reset. If recollection serves, a folder that the foxISAPI COM directed it's INI files to, was missing.
>>
>>That was probably the problem - but any info related to issues running a foxISAPI service next to a westwind service or a "connection" (docking) service would be appreciated.
>>
>>Thanks