Do not write back into configuration file about redalert HOT 2 OPEN

originally this stemmed from the desire to have a unique ID for each check. essentially the ID gets generated if not present. that said, I see you're point and I'm also of the view that the config really should be immutable..

options:
(1) rely on the user specifying a unique ID in the config
(2) ID is somewhat deterministically generated (e.g. via hashing), based on all/some of the configuration parameters. therefore doesn't need to be provided. but problematic if a config param used in determining the ID changes, resulting in an ID change

how does option one sound @jacksgt ?

from redalert.

Hi, thanks for the quick answer!

I think both options sound very good, we not even combine them? Let the user - optionally - specify a unique ID (if the consistent data is very important to them) and, if no ID was specified, generate one (the deterministic generation via hashing of parameters seems reasonable).

Personally, I will mostly specify the parameters for each check once and then let it running. Even if I were to change some parameter eventually, I wouldn't be too concerned about the 'old' data.

from redalert.