Search the list of the internet for "Cairngorm" thats the best answer :)
 
Dimitrios Gianninas
RIA Developer
Optimal Payments Inc.
 

________________________________

From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of farmetha
Sent: Thursday, December 21, 2006 1:55 PM
To: [email protected]
Subject: [flexcoders] Question on design patterns



I have built several flex applications since its initial release and
these apps have been very large and complicated. They usually consist
of components within components within components, etc. I am sure
everyone else has done the same. I have a couple of questions about
design patterns, I think I already know my answer, however I am
curious about everyone's opinion.

1) Should I put HTTPServices into components and pass urls to the
components (allowing them to handle posting data and handling the
result) or
2) Should I put all of my HTTPServices on the application level (i.e.
the primary controller) and use data binding and events to communicate
with the components.
3) Is there a better way to handle this, especially when your
component heirarchy gets deep?

Thanks for you input,

Ethan



 

-- 
WARNING
-------
This electronic message and its attachments may contain confidential, 
proprietary or legally privileged information, which is solely for the use of 
the intended recipient.  No privilege or other rights are waived by any 
unintended transmission or unauthorized retransmission of this message.  If you 
are not the intended recipient of this message, or if you have received it in 
error, you should immediately stop reading this message and delete it and all 
attachments from your system.  The reading, distribution, copying or other use 
of this message or its attachments by unintended recipients is unauthorized and 
may be unlawful.  If you have received this e-mail in error, please notify the 
sender.

AVIS IMPORTANT
--------------
Ce message électronique et ses pièces jointes peuvent contenir des 
renseignements confidentiels, exclusifs ou légalement privilégiés destinés au 
seul usage du destinataire visé.  L'expéditeur original ne renonce à aucun 
privilège ou à aucun autre droit si le présent message a été transmis 
involontairement ou s'il est retransmis sans son autorisation.  Si vous n'êtes 
pas le destinataire visé du présent message ou si vous l'avez reçu par erreur, 
veuillez cesser immédiatement de le lire et le supprimer, ainsi que toutes ses 
pièces jointes, de votre système.  La lecture, la distribution, la copie ou 
tout autre usage du présent message ou de ses pièces jointes par des personnes 
autres que le destinataire visé ne sont pas autorisés et pourraient être 
illégaux.  Si vous avez reçu ce courrier électronique par erreur, veuillez en 
aviser l'expéditeur.

Reply via email to