>>>>>If you still want to write an ISAPI app, I suggest you stick with C. For details on the ISAPI spec, check out this MIND article:
>>>>>
>>>>>http://www.microsoft.com/Mind/0197/ISAPI.htm
>>>>>
>>>>>Hope I didn't confuse you too much...
>>>>
>>>>Actually that was very helpful. Thank you.
>>>
>>>One question. Why do you suggest sticking with C?
>>>
>>>Dan
>>
>>Only because I know of no other language that qualifies for the job...
>>
>>IIS uses a strict convention of functions that must be exposed in a dll that wants to play as an ISAPI application. Simply writing a COM server with those method names doesn't work, and that's all VFP can do.
>>
>>IMHO, there is really not much reason to go through the trouble of what you are trying to do. Between ASP, FoxISAPI and tools like WWWC, VFP programmers really have all we need to retrieve POSTed and GETed variables, and to return HTML, or any other type of data in HTTP.
>
>But Strahl, did use FoxISAPI. And you're saying that its more trouble then its worth.
>
>Dan

WWWC does not use FoxISAPI. It uses wc.dll as the message mechanism between IIS and your app. Rick has written several articles on using FoxISAPI, and even rewrote FoxISAPI in C to fix a problem or two, but it is not the mechanism used in WWWC.

And I didn't say FoxISAPI is more trouble than it's worth. I was saying that with the tools already available to you, there's really not much need to write another ISAPI application to interface IIS and VFP. I'm sure that if one's needs were extremely unusual, then you might find shortcomings in FoxISAPI, ASP and WWWC that you could not get across, but retreiving form variables and returning HTML are not unusual needs, and they are provided for by what's already written.