limiting number of instances in Windows terminal server

[Schokohase]

Zitat von imadam:

Zitat von Schokohase:

Do you use a mutex?

If yes, a global or a session mutex?

This is new app. Starting from scratch. So Delphi best practice should be applied here .

You already have a working solution for

Zitat von imadam:

We are able to fix this on Windows to have only one instance of application running

so please show us it and we can tell yo how to change it for running on TS

[imadam]

Zitat von Schokohase:

Zitat von imadam:

Zitat von Schokohase:

Do you use a mutex?

If yes, a global or a session mutex?

This is new app. Starting from scratch. So Delphi best practice should be applied here .

You already have a working solution for

Zitat von imadam:

We are able to fix this on Windows to have only one instance of application running

so please show us it and we can tell yo how to change it for running on TS

I read my post again. It is bit confusing . So we started with prototype. Playing around. We were able limit this to one instance of the app on Windows Desktop. However, we would like to be able to set number of instances (like 3 for user 1, 1 for user 2) in Terminal server. Also, if is there some best practice for Delphi developing this kind of apps, it would be great if somebody can share it. Let me know what to share ...

[Schokohase]

Zitat von imadam:

We were able limit this to one instance of the app on Windows Desktop.

I guess you use a mutex for that.

For Terminal Server (or even in generell) do not use a global mutex as this would be for the whole system.

For an application with one instance you need one mutex.
For an application with two instances you need two mutexes.
...

[Klaus01]

.. but whith muutexes you have to decide how many instances can be started - at design time.
These settings are then based on application level - not on user level.

best regards
Klaus

[mjustin]

Did you try TJvAppInstances already? It is designed for limiting app instances, and it allows to set the maximum number of simultaneous instances using the property MaxInstances. I am not soure however if it is also suited for a TS.

[imadam]

Zitat von mjustin:

Did you try TJvAppInstances already? It is designed for limiting app instances, and it allows to set the maximum number of simultaneous instances using the property MaxInstances. I am not soure however if it is also suited for a TS.

We tested this: http://www.delphidabbler.com/articles?article=13&part=4 and this works on Windows 10 limiting to 1 instance. But it doesn't work on TS. It actually on TS allows only one user to run only once instance. Whom ever get first to it

[mjustin]

Zitat von imadam:

Zitat von mjustin:

Did you try TJvAppInstances already? It is designed for limiting app instances, and it allows to set the maximum number of simultaneous instances using the property MaxInstances. I am not soure however if it is also suited for a TS.

We tested this: http://www.delphidabbler.com/articles?article=13&part=4 and this works on Windows 10 limiting to 1 instance. But it doesn't work on TS. It actually on TS allows only one user to run only once instance. Whom ever get first to it

Ok, the code on (http://www.delphidabbler.com/articles?article=13) does not use the JVCL TJvAppInstances, but good to know

I also posted another suggestion (see #18)

[imadam]

Zitat von mjustin:

Did you try TJvAppInstances already? It is designed for limiting app instances, and it allows to set the maximum number of simultaneous instances using the property MaxInstances. I am not soure however if it is also suited for a TS.

No, I haven't tested it. Will review. But on initial aim, this won't help.

[Schokohase]

TJvAppInstances will limit the applications inside the SESSION.

So => yes, this will work on TS too.

But, a single user can open more than one session on a TS (you can limit it optional to only one session per user).

[Dalai]

Zitat von Klaus01:

.. but whith muutexes you have to decide how many instances can be started - at design time.

Uh, no. A Mutex is based on a name, a string, and strings can be built at runtime. Example from one of my projects where the mutex name is based on a concatenation of several strings:hMutex:= CreateMutex(nil, True, PRODUCTNAME + PRODUCTNAME + PRODUCTCOPYRIGHT); Using usernames and an appended counter instead is trivial. Reading the information that user A can start the application X times and user B can start it only once is trivial, too (Registry, INI, XML, whatever). Use that in conjunction with a for-loop that tries to create mutexes until either all of them already exist, or the maximum allowed instances are reached, and you have reached your goal.

Regards
Dalai