Naw. Commands aren't necessarely needing to be created that way. You could, but for larger apps, you'd end up with a LOT of Commands. However, it's not too tough to re-factor because if you coelecsed many Commands into one, you'd really only need to change the Controller's addCommans function.
So, if you want to start that way, sure, go for it. For smaller projects, it'll make it easier to identify what Command does what, and you won't have to use custom responders in your Command's either if your Delegate only does one thing. For larger projects, however, you'll end up having many Commands doing similiar things to similiar data; it's just easier to combine them in the same class so related code is nearby for reference and/or sharing. Same goes for Delegate's. A common strategy we've done is mapping our Delegate's to CFC's; some of our CFC's, have say, 8 methods. 1 Delegate will have 8 public methods. ----- Original Message ----- From: "ben.clinkinbeard" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, July 06, 2006 10:37 AM Subject: [flexcoders] Re: WebService & Cairngorm 2 Example Very cool. That all makes pretty much sense. I do have another question (shocking, huh?) about why you would have a single command support multiple events/use multiple delegates. Isn't the point of Commands to have a class that does one thing (and nothing else)? Thanks again, Ben -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
