Terry,

>My project is not a VFP web-store or VFP web service application. There is little (to no) need for dynamic HTML. Sometimes "browser" states will require a "dynamic" string of JavaScript targeted for launch from a "hidden" frame using CSS to affect "page" controls.

A few more things to consider before you arrive at a final architecture...

Do you have any particular security and/or login needs? If so, how will you check login and password against some data store?

How will you track the "state" of each user and will that be more effectively done through Session variables or data table entries? For example, if you progressively get input from the user over several pages and need to do something with it a some end point, do you really want to drag all that data around in hidden form vars or session vars, or would it be better to store it in a table at each step?

Is there conditional logic that needs to redirect a "hit" to a dynamically determined next page? If so, can the JavaScript handle that, or does it require something more capable?

Bottom line: it might be some small, but difficult, part of the project that points you to which technologies to use for the dynamic stuff. I once worked on a site where almost all the pages were static HTML, but special logic was required to bounce users to either the public site or the private site to find the correct version of the HTML file. I did that with a login (unless the user had allowed a permanent cookie) and trapped in WC the incoming requests for HTML static pages (by use of a different file extension that was script-mapped to WC.dll), checked for private site requests where the user was not logged in (automatically or manually), and redirected to the corresponding public page if it existed, and otherwise sent them to the login page. Maybe it could have all been done in JavaScript, but working in VFP code in WC made it a much more palatable project.

If you have any specs for this project that will require anything unusual in the conditional processing or state-tracking, you will probably enjoy working with a stable and well-supported "web plumbing" product that contains simple-to-use provisions for state-tracking and allows you to call VFP code. My suggestion in this case is to avoid FoxISAPI and go with WC, since they already have it installed.