01-25-2024, 01:51 AM
Yes, this was a kind of a "fix". Some properties have been historically "open" to be changed during application life cycle, but it actually shouldn't (because 2 threads shouldn't be updateing values concurrently).
So, you can change the WebApplication.SessionTimeout value individually, but you can't set the global SeverController.SessionTimoue after the applicaiton has started (you still can set it during OnConfig event of ServerController)
So, you can change the WebApplication.SessionTimeout value individually, but you can't set the global SeverController.SessionTimoue after the applicaiton has started (you still can set it during OnConfig event of ServerController)