The resulting COM EXE should be set up to be SingleUse in the project menager for use with FoxIsapi. FoxIsapi contains a pool manager which handles the instancing and queueing of requests.

Others may have more info on trying to use MultiUse COM EXE's with FoxIsapi.

Bill

>I would appreciate it if anyone can give me some hints on the following:
>
>My VFP6 Project contains 15 public classes; each one is an OLE server configured in the Project Info to have Multi Use instancing. Upon compiling the project, the classes are registered in Winnt4 Registry and the Dcomcnfg has them run by the Interactive User. The FOXISAPI.ini file has some declarations and an entry for each class; they look like this:
>[foxisapi]
>busytimeout = 10
>releasetimeout = 14
>statusurl = Status
>reseturl = Reset
>SingleModeUrl = SingleMode
>MultiModeUrl=MultiMode
>DefaultServer=myexe.mylogonclass.mystartupmethod
>
>(then each public class has its own set of the next 2 lines)
>[myexe.myclass]
>myexe.myclass=3
>
>When I hit on myexe from a web browser url, everything loads perfectly fine, and the exe process remains alive in the webserver, to be used by subsequent hits. The exe returns the desired html output.
>
>The problem starts when multiple users hit on it at the same time. Although most of the time it is able to handle all the requests, sometimes it does not return HTML output to the browser, but if the internet user clicks a second time making the same request, the desired output is received. When the first request is not returned, a FOXrandomname.ini file is created on the webserver hard disk. My users can live with occasional need to "click again" when the first request is lost, but it is annoying. Any ideas anyone?