12-10-2021, 06:28 AM
(This post was last modified: 12-10-2021, 06:29 AM by Alexandre Machado.)
To stress test IW applications I basically use 2 tools: (a) Mostly Apache JMeter which is somehow difficult to configure correctly, but once it's done is simple to change/adjust, and (b) an inhouse tool created with Indy that hammers the application with some specific requests. Unfortunately it's not possible to make this tool public at this stage.
You mentioned that "what remains is just a write in exception log method, accessed thru critical section". If you have the IWExceptionLogger active, why do you need another exception log?
Have in mind that adding critical sections to a multi-threaded application is a double-edged sword: you protect it from concurrent access but you also increase the chances of an undesirable dead-lock...
Regarding your ServerController settings, everything looks good to me, except the
CookieOptions.SessionCookies := false;
unless you want the session cookies to persist when the browser is closed. In general it's a better option to set it to True, so whenever the browser is closed (not only the browser tab) the user will be forced to authenticate again.
You mentioned that "what remains is just a write in exception log method, accessed thru critical section". If you have the IWExceptionLogger active, why do you need another exception log?
Have in mind that adding critical sections to a multi-threaded application is a double-edged sword: you protect it from concurrent access but you also increase the chances of an undesirable dead-lock...
Regarding your ServerController settings, everything looks good to me, except the
CookieOptions.SessionCookies := false;
unless you want the session cookies to persist when the browser is closed. In general it's a better option to set it to True, so whenever the browser is closed (not only the browser tab) the user will be forced to authenticate again.