Farshad Mohajeri

Hi, Currently, you can only define one EXE for each Hyperserver instance. If you have multiple DLLs you need to set up a separate Hyperserver instance. In the future, we will allow same Hyperserver instance to load more than one EXE. This feature will be implemented.

Hi, Have you set the Pool Identity to LocalSystem? http://www.unigui.com/doc/online_help/using-a-different-account-for-.htm

Also, in your Node app ServerModule->AutoCoInitialize must be set to True.

Hello, Is it same if you deploy your app in DLL form without using HyperServer?

You can easily do it in support portal.

Hi, Have you opened a support ticket for this?

You need to use Blocking version of prompt. function Prompt(const AMsg, AValue: string; DlgType: TMsgDlgType; Buttons: TMsgDlgButtons; var UserValue: string; MultiLines:Boolean): Integer;

Hi, In order to trace the problem, we need to know how to reproduce it. Can you please share a sample project?

Probably we need to make it more clear in future versions.

Hi, The tab that you are looking at is about sessions running on the HyperServer itself. Please switch to HyperServer tab to see information about running Nodes.

Hi, Nothing has changed in 1.50 in regards to above components.

Stand alone mode normally should be used only for testing not production.

SendFile() yapmanız lazım, ancak o bir Session varken çağrılabiliyor.

Under a typical scenario maximum number of concurrent HTTP connections can only be a few hundreds. However, concurrent connections should not be confused with number of active sessions. You need an active HTTP connection only when a request is pending. You may have thousands of sessions, but only need 100 active connections to serve all those sessions. uniGUI internally implements pools for threads and transport handles to smartly manage OS resources. We have stress tested our own customer portal application with HyperServer in a dedicated test server with up to 2.000 concurrent sessions. As long as your server resources allow, you can increase number of sessions to 10.000 or more. The only concern here is database connections which must be pooled using pooling techniques provided by your data connection library. For example, if you are using FireDAC then you must enable database connection pooling if you plan to have more than 500 concurrent sessions.

Hi, You're question is valid. Current implementation of HyperServer supports Nodes only inside one physical server. It is similar to IIS Web Garden. Next step is to extend HyperServer functionality for Web Farms. It is in our todo list and preliminary work is already done. We are taking scalability very seriously and constantly work to increase number of concurrent sessions.