: On the functional side, it might be beneficial to keep the newInstance as is : but introduce an initInstance. : We might want instances to be initialized with some of their current : arguments before we set the core.
that was kind of my main point ... i just got sidetracked by the sexiness of an approach that violated the contract i orriginally proposed. i don't have any strong opinions about naming conventions, or specific approaches ... just that while it makes sense to init() objects as we construct them (when we are parsing the config that identifies them and has their args), we need to delay telling them about the core until the core is ready. any special "init" type actions they want to take once they have the core can be done in the "tell" function -- as long as we garuntee "init" is called before "tell" is called before any work is requested. -Hoss
