Jos,
Foxweb seems to be solid and have a large user base. It's also the oldest VFP web product. Another good thing is that it has always used memory to pass web variables from the web server to foxpro as opposed to text files(using text files for communication has always had serious drawbacks) - I believe it originally did this with DDE and now uses Named Pipes.
I actually first got involved with vfp web technology when the developer of Foxweb posted his code on the web in '94 or '95 which I thought was extremely cool.
It suffers some of the same negatives as other .EXE based servers. You have to be aware of and monitor the .EXE servers in the background and you have to manually start/stop them or use SRVany (which is sort of a hack compared to using COM). The isapi version should always be used for Foxweb instead of the CGI version for scalability reasons.
My opinion is that using vfp mtdlls is much smoother and faster than Foxweb at this point. Pretty much all of the early VFP .EXE web server technologies, both from Microsoft and 3rd parties, were developed (hacked you might say) to get VFP to work on the web. VFP mtdlls are definitely an improvement in this regard, IMHO.
>Hi Claude
>
>PMFJI but I am interested to hear your opinion of FoxWeb which I have used for several years and have found to be a very stable, fast, and flexible solution for my VFP backends. It comes with good documentation and good technical support. Would you care to comment and share an opinion on this vs. other options?
>
>Thanks
>
>Jos
>
>
>>Rick,
>>Sorry, if I have an opinion I'm going to give it and not according to your terms. If you remember, this thread was about foxisapi. You're the one that jumped in and felt you had to defend your own technology.
>>While you have done some very good work, I feel that you tout your own technology at the expense of moving forward with what's coming out of Microsoft. Could it be that this is because you're afraid developers won't need and therefore won't purchase your products?
>>BTW, as you know, vfp mtdlls also work with ASP.NET. It's only through the active discussion of web development in this environment that problems can be found out and solved. Scaring people away from developing in this environment does the community no good as I would think everyone agrees that we would like to see vfp continued to be used in the future and with the latest technologies...
>>
><snip>