We have a good basis with versioning. 99% of the time, workers are the ones accessing the configuration. They are at the top level.
It happens that they do access configuration through the workers service name space. In fact through a single fn ... Passing a version number when pulling out a resource is feasible. This could override the default (the current config established at startup). I want to make it clear, we never intended to do this BUT it happens that we need a way to compare configs. It's not implemented yet. It maybe more or less an unconscious design decision that makes it easy to implement. Versioning is mainly a way for us to revert back to previous configs but it's also a way to fake an immutable config state. It's an operational requirement more than a code or design issue. Luc P. > On Fri, Dec 27, 2013 at 10:35 AM, Softaddicts > <lprefonta...@softaddicts.ca>wrote: > > > Passing this stuff around using one of the two methods you have shown > > would have been cumbersome and unmaintainable. Most of the time > > our configuration information comes from top level fns so the lower > > layers remain even more insensitive to how this info is pulled in. > > > > Agreed. Now imagine that one day you realize that you have a problem that > can't be solved with one single configuration for the entire lifecycle of > the program, but somehow, you have to process and compare results from two > configurations simultaneously. What would you do? How painful would that > change be? Is there something we can do to make this more feasible in > Clojure? > > -- > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- Luc Prefontaine<lprefonta...@softaddicts.ca> sent by ibisMail! -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
