Yes, that’s basically the end goal.
Yes, I also considered storing the values in a file and reading that file at execution time. I even thougt about using a database.
However, it’s “just” around 100 values.
So I decided against the database solution, since that would possibly be too much of an administration and performance overhead.
I also decided against the file-based solution due to the administration overhead. You now maybe wonder: what overhead? Well, I would then also have a file on the filesystem, which I have to administer. That wouldn’t be the problem if I would be the only one to administer the IS and the other involved admins would be as disciplined to use Deployer, etc. in order not to forget about this file lying 'round somewhere (well actually not somewhere, but e.g. in the resouces directory of the package).
Anyway, if relying on an external file, you also have to be careful when turning on the results cache.
Thus, I opted for the in-service solution, even if it is not the best one - also from an administration point of view… (What if the list has to be updated…)
Thanks for your useful input,