Howdy, I am running into a design question. I have been doing a lot of thinking about this, and haven't come to any conclusive answer. I always have issues with composition because its seems like it adds quite a bit of complexity to applications, surely it helps with Code reuse, but it goes against my (Keep It Simple) style of application building. You start adding complexities, and things become brittle. My question is, lets say I have a person.cfc whose composed of normal instance vars and an address.cfc (wow I have really beat this example to death). Looks good to me. However, I also took Sean's get/setMemento() concept from his mach-ii sample app (Sean's stuff is good, and I hate dragging him into my convoluted questions. I just feel obligated to cite my sources). If your object is Flat, meaning its not composed of other objects, memento is really slick, clean and tidy. Just set, or get the instance vars. But once you introduce composition, its gets a bit uglier. Can anyone help ease my fears about composition, possibly an example of how folks have used the memento concept with composition. I am guessing its much like Barney suggested to me a while back when I asked about serialization. To me it seems like a tradeoff of flat stability, or complex reusability. Hmm.....any thoughts?
Thanks much, Justin ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
