AristosQueue wrote: drjdpowell wrote: It would be much better if the Voltage actor could be designed independently of any caller, with each caller able to specify how it would like to access the information.
*sigh* Take a hint, folks. As Martin said in his post at the top of this page: "I think with the AF in particular it is pretty hard to get started as there is such a breadth of views on how/when/whether to use it." So stop trying to make his life harder by adding complexity to his design! No, it is not necessarily "better" to increase the flexibility of the system. There may be reasons to do so, but a big reason not to do so is if that kind of code reuse isn't necessary. For example, if the actor is just a shell around the core device API, creating a custom shell for this particular app that will never be reused elsewhere is more than appropriate. And there are plenty of other reasons. |
Sorry, should have specified that I was commenting on the framework, not what Martin should do. It would be better if the framework was such that Martin could easily design his Voltage actor, and not have to deal with the complexity of adapting it to a specific caller's precise needs.
