As Erik pointed out, Web Connection has very little to do with FoxISAPI.
In fact, Web Connection has been around much longer than FoxISAPI and WWWC
provides much more functionality than FoxISAPI can - starting with the ability
to build your application interactively in VFP, instead of requiring you
to use COM from the start (you can later compile your app to run COM).

Web Connection's implementation of the COM interface is different (and I think
more flexible and efficient) than FoxISAPI and includes many additional
safe guards and administrative features that you will not find in *any*
other product. Things like automatic recovery from failed or hung servers,
live online code updates without taking servers down, full remote management
of all servers and much more.

I can understand your concerns about the future of Web Development. There's
always going to be new stuff, so waiting until things settle down will simply
waste your time waiting <s>... no offense, but the way to go is to start now.

Things have been moving very quickly for the last few years, and now is about
as close as I can think of being settled down as it's been. Web Connection
isn't the only game in town for sure. Especially, Active Server Pages from
Microsoft is a big draw, but I think for people who want to use VFP for
their main code base in Web apps, and build applications quickly and efficiently
Web Connection fits that bill better than ASP. I hate to boast, but I
guarantee you that a proficient VFP programmer will be many times more
productive with WWWC than a proficient ASP/VB developer is in ASP.
And with WWWC you'll build a more robust application in the process.

I work with both - and if I have the choice ASP is not the first choice (if
there are occasions where WWWC doesn't fit the bill - it's to pure ISAPI
and C++).


I have an obvious bias, but I'm also another user who builds applications
for clients and I use what works best for the job to make the best of my
time.