Michael Bernstein wrote:
Thanks, Steve. That was very helpful. To summarize your explanation, if I understood correctly:
This is strictly an implementation issue.
You could say that. I would agree some of the time :-)
If the SkinScript has functionality that should be shared by more than one Rack, it should go in the Specialist,
Not quite. If the SkinScript has functionality that is shared by all the Specialist's Racks, then it should go in the Specialist. Another way of looking at this is that application logic lives in the Specialist, and storage logic lives in the Rack.
otherwise keep it with the Rack that it's specific to. Or, looked at another way, common functionality should be factored out and acquired.
Although you can do that, it is not always the best thing to do. Sometimes, a bit of redundancy helps ease a system through the pains of evolution :-) -- Steve Alexander Software Engineer Cat-Box limited http://www.cat-box.net