Started by RDMTECH, October 09, 2008, 04:47:43 PM
Quote from: Hotrod on October 11, 2008, 07:49:10 AMCare should be used in implementing such a thing. There are some circumstances when multiple instances of a process are desirable and maybe even necessary. Maybe a choice of the number of allowed instances of a given process would be more usable.
Quote from: RDMTECH on October 16, 2008, 02:00:58 PMAre you limiting instances per session ID?
Quote from: RDMTECH on October 16, 2008, 05:23:25 PMWhat's left before you take 3.17 final?
Quote from: RDMTECH on October 17, 2008, 03:46:21 PMI just purchased 15 licenses. I'll wait for version 3.18 to deploy. Thanks for the hard work.
Quote from: RDMTECH on October 17, 2008, 11:05:23 PMI found some anomalies.
Quote1. If a process is already past its instance limit when you configure it won't close processes until it gets down to the limit. That may be a good thing, but I can see when it would be desirable to close the additional instances to get down to the limit you set. Maybe you could alert the user that the current limit is less than the number of current instances and ask if you want to close processes until you get to the limit? Maybe pop up a list of the processes and let you choose which to close.
Quote2. If a process is already past its instance limit when you configure it will allow additional instances of the processes to be opened. 3. If a process is already past its instance limit when you configure and you close all instances of the process it won't limit until you restart the core engine. 4. It appears that any reconfiguration of the instance limitation requires a restart of the core engine.
QuoteI'm a bit hesitant about deploying. I could set the limits and restart the core service, but I would like your thoughts first.
Quote from: RDMTECH on October 27, 2008, 01:37:01 PMExcellent....I'm looking forward to the next beta!!