What you will find is that the overhead of the particular product you use (FoxWeb, or Web Connection) will be negligible (hundredths of a second). Depending on your application, most of the latency will be caused by the network (unless your application is deployed on an intranet), or by the application code itself.
Application code will be equally fast (or slow) regardless of whether it runs in a FoxWeb or Web Connection page, or a traditional VFP desktop application. All three use the native VFP engine, so script execution performance will be identical.
FoxWeb Support Team
support@foxweb.com email |
Sent by mary g on 10/23/2007 05:16:28 PM:
Thanks for all the great advice! Now I have sort of a follow up question.
Has anyone used both FoxWeb and Web Connection and could offer a comparison of the two.
I am particularly interested in speed- our app uses wizards to obtain results in dbf format.
It would also be helpful to know if there are any other competitors in this arena that have been updated for Visual FoxPro 9.
Mary
Sent by mary g on 10/19/2007 04:55:56 PM:
I need some help with figuring out how to port a desktop application to a web application given these constraints:
1. Desire to maintain a base of common code between desktop and web applications
2. Desktop code is mostly procedural, not object-oriented (originally written in FoxPro 2.6), and does not separate interface from business logic.
3. Preference to make as few changes to desktop code as possible
Is this feasible? What are my options? Any suggestions would be most apprecitated.
Mary