As with anything it all depends on what you need to accomplish and how you want to work. For that 'someone' to tell you that it's bad is just foolish because they likely don't have the foggiest of ideas of what you're doing and how FoxISAPI even works.

That said it is true that FoxISAPI is aging technology that hasn't been updated, but remember that just because something is old doesn't mean it doesn't work any longer or can't do what other tools can do.

I'm not a big fan of FoxISAPI any longer for a number of reasons most of them having to do with the style of work, but it works nevertheless.

+++ Rick ---







>I've built a VFP com server that is rendered by FOXISAPI. Although my com server is NOT West-Wind's WebConnect, it IS based on West-Wind's wwFoxisapi classes as specified in Rick Strahl's book and white papers. I'm very pleased with my creation - it works great.
>
>Recently, someone told me that what I have is "bad" and that I should be using something called PHP - I guess this is a scripting language. I know very little about PHP. I was told that a PHP approach is better because it can access data from any backend datasource, regardless of the operating system on which the data resides. As far as I know, FoxIsapi works only on a Windows server running IIS. I was also told that a Unix based webserver is better for a variety of reasons, but mostly because its more secure.
>
>Is there any truth to this? Does anyone know more about PHP? I really like my Foxisapi approach (mainly because I understand it and it works - at least on Windows/IIS) I was given no specific about what exactly is better about PHP - just vague terms like "more secure" and "more versatile across multiple web platforms" etc, etc. I'd like to be able to "fire" back at this critic with some facts about PHP vs. Foxisapi. Any help would be a great help.
>
>Alan