As a follow up, what you're really asking for is some sort of recipe that you can apply, and there isn't one. As we've tried to get across several times now, the design depends on the context and use cases.
On Tue, Feb 17, 2009 at 4:26 PM, Henry Ho <[email protected]> wrote: > To use a super abstract example, it'll be like.. > > 1 ObjectA has an ObjectX, ObjectY, and ObjectZ. > > ObjectX, ObjectY and ObjectZ have n public methods each (where n may be = > 10+). > > If I push all behaviors onto ObjectA, then A will have all 30+ public > methods (+ its own). Yes, we'll respect the Law of Demeter, and no one will > know ObjectA really has ObjectX/Y/Z, but wouldn't ObjectA become super fat? > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
