LTConfig::Field::get_values question

You may want to isolate this LTConfig code from other parts of your application so it is easy to switch out. We have gotten requests for canned (specific) interfaces for some of the items now supported via LTConfig. We are evaluating whether it is actually worth spending heaps of effort to make an internal bridge that would make the old LTConfig access work if and when we do this.

 

 

While thinking about this, I posted a query some months ago asking who was using LTConfig, and got either no response or minimal response (can't remember) -- that suggested the answer would be people would welcome a canned interface and we'd disappoint pretty much no one if we simply discontinued the LTConfig access ("killed" or "deprecated immediately") rather than following our normal deprecation policy. LTConfig has always been a little less conceptually secure in terms of changes than the rest of iControl, since it is a window to stuff behind iControl internally, yes, like the rest of iControl, but in this case we get run-time failures if the stuff changes behind iControl rather than compile-time. iControl has a very extensive regression test suite, but I don't off the top of my head remember how extensive our checking of the LTConfig classes is.