We actively use the purchased WebConnection (version 8.2) in development. Currently, we have encountered the following problem. We are trying to test an application on WebConnection and IIS Express under load. And it looks like WebConnection processes incoming requests in single-threaded mode. That is, when one incoming request is processed (endpoint method is called), then all the others that arrived during the processing of the first request are in the queue in waiting mode. And each subsequent incoming request is processed only after the current request is finished processing. Therefore, we have several questions:

• are there any WebConnection configuration parameters that allow you to manage the modes of processing incoming requests?
• are there any built-in tools in WebConnection for scaling high-load applications?

Thank you for your answer.

Yes that's the way it's designed. At the end of the day FoxPro is a single threaded application and can only run one instance effectively at a time. Each Web Connection server instance serves one request at a time.

However, you can run multiple server instances in a pool that can serve requests. In production you can use COM servers where you configure a pool of servers that is auto-loaded and then provides n number of simultaneous requests.

Here's more information:

Understanding Web Connection Servers in Production

+++ Rick ---

Thanks for your reply. The link you provided is unfortunately broken. But I found the documentation here: Deploying your WebConnection Application

Are there any licensing restrictions on the number of copies of COM servers running in a pool?

Try the link again...

• Understanding Web Connection Servers in Production

Licensing is explained here:

• License

+++ Rick ---