Thierry,

Thanks for the kind words re: Web Connection.

Yes you can definitely make all this work, but it requires a lot of understanding on how things work below the surface. It's not easy compared to other technologies where you simply write your code, upload it to a server and it just runs.

Also performance of VFP in server applications is really abysmal - it requires a bunch of trickery to make VFP even eek out a few hundred requests a second, when a .NET app can easily churn out 30,000 req/sec in the same environement. Granted most application don't need that kind of throughput, but it tells you something about the scale in terms of what the overhead of COM VFP interaction with a Web server costs.

I have live .NET apps that run full data app requests at several thousand req/sec on a single dual core box and it's barely pushing the server. That's simply not possible with FoxPro. You can make that work too - but it requires a lot more horsepower and scaling out to multiple boxes.



+++ Rick ---

>> It works and can be fast, but it really doesn't scale easily.
>>+++ Rick ---
>
>Rick,
>
>You're too modest!
>
>In my experience, VFP web applications based on West-wind Web Connect such as FoxInCloud applications do scale very easily and consistently (even on older versions of WWWC such as 4.68).
>
>For example, here is the profile of a business critical FoxInCloud application in production :
>- 6 load based COM servers
>- 35 forms/1,200 objects instantiated in memory
>- 80 remote views and cursors / 60 datasessions
>- 1,400 AJAX user events
>- up to 30 concurrent users
>- 35,000 requests per day, tallying over 1 billion VFP instructions executed
>
>This application typically runs a full working day without a single error.
>
>Just recycled every morning at 3 PM using the standard IIS application pool recycling mechanism
>
>Note: the fact that IIS offers so many recycling options denotes that all Web app systems need recycling, including asp.net