Agreed, no problem here.

-TH

--- In [email protected], "Dimitrios Gianninas" 
<[EMAIL PROTECTED]> wrote:
>
> Just read the article, seems much cleaner, something definitely 
considering.
>  
> Also don't think its much of bother going from 1.x to 2.0, there 
are many changes to make upgrading anyways :)
>  
> Dimitrios Gianninas
> RIA Developer
> Optimal Payments Inc.
>  
> 
> ________________________________
> 
> From: [email protected] 
[mailto:[EMAIL PROTECTED] On Behalf Of Steven Webster
> Sent: Thursday, July 06, 2006 3:53 PM
> To: [email protected]
> Subject: RE: [flexcoders] Re: WebService & Cairngorm 2 Example
> 
> 
> 
> Darron makes some very fair points; our reasoning for the current 
Cairngorm implementation was driven from some findings we had during 
the beta, which no longer seem to apply.  We'll have some discussion 
internally to reinforce our decisions, but Darron's approach seems a 
sensible and valid one that we may likely end up bringing into the 
main codebase.   
>  
> How would folks feel about us making that change ?  We're always 
very reticent of API changes for backward compatibility.....would 
folks be ok with this one ?
>  
> Steven
>  
>        Steven Webster
> Practice Director (Rich Internet Applications)
> Adobe Consulting
> Westpoint, 4 Redheughs Rigg, South Gyle, Edinburgh, EH12 9DQ, UK
> p: +44 (0) 131 338 6108
> m: +44 (0) 7917 428 947 
> [EMAIL PROTECTED] 
> 
>  
> 
> 
> ________________________________
> 
>       From: [email protected] 
[mailto:[EMAIL PROTECTED] On Behalf Of ben.clinkinbeard
>       Sent: 06 July 2006 16:07
>       To: [email protected]
>       Subject: [flexcoders] Re: WebService & Cairngorm 2 Example
>       
>       
> 
>       Darron Schall just posted a great article about Cairngorm's 
Responder
>       interface and what he considers to be a better alternative.
>       
>       http://www.darronschall.com/weblog/archives/000234.cfm 
<http://www.darronschall.com/weblog/archives/000234.cfm> 
>       
>       
> 
>  
> 
> -- 
> 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.
>







--
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/
 



Reply via email to