Rick, thanks for the detailed explaination.
It won't be any simultaneous requests. What I am trying to do is a web based monitor that will show a progress of some processes. Ideally I would want to push data to the browser without pulling one from it.
>Mark,
>
>No and you shouldn't.
>
>If you're calling this from an ASP or ASP.NET page you should build your server as an MTDLL not an EXE and then let it release on each hit. This is reasonably efficient - in fact more more efficient than leaving a server running because any instance that is kept running must be marshalled to a particular thread on every hit, which is very expensive.
>
>In theory you can do this by storing an object into the Session object which hangs on to a reference and keeps the object alive. This is a REALLY bad idea though because you'll end up with many instances and the marshalling above will kill the server with just a few simultaneous requests.
>
>Pooling like this can be done, but not with ASP/ASP.NET default handling.
>In ASP/ASP.NET it's actually more efficient to use create/dispose cycles. You do pay a price for this though - anytime an object is loaded it has to reload its state (Init fires each time). Depending on what you do in the Init() this may have overhead. Also connections need to be reestablished and data caching is lost with each instantiation.
>
>But from a pure COM load/unload perspective MTDLLs are very efficient at loading unloading COM servers.
>
>
>+++ Rick ---
>
>>I have a web app. that has the following structure:
>>html forms are submitted into same asp page that creates an object from the VFP exe module for all the data processing.
>>Here is an asp page:
>>

>><SCRIPT LANGUAGE="JavaScript" RUNAT="Server">
>>var oComObj = new ActiveXObject('webconnector.connector');
>>oComObj.minitiate(Server, Request, Response, Session);
>>oComObj.mDispetch('scanmonitor', 'frmscanmonitor');
>></SCRIPT>
>>

>>Is it possible to keep VFP exe runnning after the http request has been processed?
>>
>>Thanks