>1. It's (according to Rick) about 10 times slower than VFP with Web Connection,

Hold on there big boy! <bg>

I never said that. It depends on what you're doing, but typical COM objects running from an ASP page and the same thing running in Web Connection under load will run two to three times faster in terms of request overhead with a HelloWorld type request. These are real numbers I tested in 8 hour load tests with WAST a while back with the same code running in both ASP and WC.

As to actual speed of the Fox code in a WWC app and an ASP COM object - that'll obviously be the same. We're talking about overhead between the Web server and the Fox app here. It happens that ASP has to reload a VFP object on every hit, while WC does not since objects are pooled. This loading and unloading takes a huge hit on the Web server which causes typical results to be 2-3 tiems faster with WC.

The 10 times slower probably was a comment about certain script operations like walking an ADO recordset as opposed to running a Fox query and building a string in VFP or using WC's templates to build the output - the difference there is quite dramatic, but that's to be expected because VPF rocks on database access, walking the data and buildign strings.



> 2. Using Web Connection let's me step through my code in the familiar debugger and 3. Why regress to foxbase style debugging?


Well, that's another story <s>... frankly, I just can't imagine doing things the ASP way for anything serious. I fret about the wasted time. I can literally be 10 times more productive with WWWC than in ASP.


FWIW, with WC 3.0 you can build and debug your app in Web Connection and then use the application as an ASP COM component - if you want to slow your app down this is a good way to go <bg>... but for those that have to say 'we used ASP' you can do that with Web Connection too.