|
What I do is typically is have one delegate that groups
server interaction for every specific portion of the app. So one delegate is
used by several commands. For an example ticketing app I'd have a UserDelegate
(for specific user interaction, might have several method) and TicketDelegate
(has several methods for interacting with a server... ex.: create, update,
etc...)
Hope that helps.
Dimitrios
Gianninas
RIA Developer
Optimal
Payments Inc.
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of flxcoder Sent: Monday, August 14, 2006 2:01 PM To: [email protected] Subject: [flexcoders] Cairngorm:One controller, so many commands, so many delegates, so many events Now I have about 4-5 events that correspond with the app server and
-- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
YAHOO! GROUPS LINKS
__,_._,___ |
- RE: [flexcoders] Cairngorm:One controller, so many com... Dimitrios Gianninas
- [flexcoders] Re: Cairngorm:One controller, so man... Jason
- RE: [flexcoders] Re: Cairngorm:One controller... Dimitrios Gianninas

