Then when the 4.0 UI came along, which was another complete ground-up rewrite, and leaning even more into crazy ideas, we needed a cleaning product name that gave this same sense again, but this time with "oxiclean" in the role of the safe alternative. The idea was that "pinesol" was good ol' dependable stable pinesol, whereas that "oxiclean" product was amazing, but ok it might damage or possibly ignite your sweaters, who knew. So the "search" directory suddenly became a dynamic choice made at runtime between "search_pinesol" for the old 2.0 UI, and "search_oxiclean" for 3.0 UI. A minor detail of the scheme was that a directory name had to be given to each UI available, and cleaning product names were chosen as a nod to the ajax craze at the time. This allowed the stable 2.0 UI to coexist with the then-newfangled 3.0 UI. If I recall correctly you could change which one was active on the CLI. Thus a mechanism was built to allow the whole front end to be swapped out. When the implementation of Splunk 3.0 got underway, the ability to run either the old stable 2.0 User Interface or the new UI was key for many reasons.
0 kommentar(er)
