Chris,
You may want to consider using VFP with ASP and ASP.NET instead of FOXISAPI. We've found it to be much more stable and easier to install. It works a lot like FoXISAPI, has incredible performance, and is an easy sell to clients as an ASP or ASP.NET component. Check out the resource page and demos at www.activevfp.com if you're interested. BTW, it's still pure VFP code for your VFP web applications...
>Hi all,
>
>I am in the process of converting our web engines from X-Works to FoxISAPI.
>
>The code itself has been pretty much fully converted. But i am having some performance issues with FoxISAPI.
>
>To begin with, As per Rick Strahl's articles, I built as an Out-of-Process EXE, when I had my initial build as an in process (due to incorrectly remembering the article) it would constantly hang IIS, and requrie a reboot.
>
>As an Out-of-Process, It does not hang IIS, but occasinally hangs FoxISAPI (or itself), requiring a IISRESET.
>
>I then noticed however that the COM object would release itself after each call, so it would need to reestablish connecitons to the tables etc. Which was taking sometimes up to 20 seconds. (When going across network)
>This is obviously no good, and logging showed that it was indeed that opening of tables that was the cause of the slow down.
>I was setting lnReleaseFlag to 0, so i didnt understand why it was releasing itself.
>
>So since then I have had the idea of embedding it in COM+,
>So I rebuilt as an in-process DLL, and created a new application for hosting it in COM+.
>
>When it runs, it goes very quickly, and leaves its connections open etc. which is all good.
>
>However I seem to get a lot, ie about every call other then the first,
>

>HTTP 500 - Internal server error
>Internet Explorer.
>

>The main page, and 2 of the frames on it are all generated by the COM,
>The main page and One frame loads, the second does not, and all other calls do not.
>
>Is there an Issue with using COM+ and FoxISAPI,
>Any suggestions on what could be causing it?
>
>Thanks,
>-Chris