The book in general has some best practices to pretty much everything. 
But your CF approach sounds good; we're in a similar situation in that 
we have a large knowledge management system built in CF - there will 
never be a plan to redo that in another language, and the flex stuff we 
build just adds onto the existing 'product'.

[EMAIL PROTECTED] wrote:

>Thanks for the advice, Tariq.  I ordered the book last week and am looking 
>forward to giving it a read.  Does the book give examples on how to create a 
>result handler? In terms of CFCs, I'm converting a MVC Fusebox 4 coldfusion 
>app to a Flex interface.  Since the application is allready very large and 
>there are already thousands of programming hours put into the controller and 
>model sections, I wanted to re-use as much of my CF code as possible.  My idea 
>is to call CFCs that will have a number of cfincludes, mimicking a fuseaction 
>as close as possible.  I realize this will lead to very tight dependency on 
>CF, but I'm committed at this point.  Do you see any other drawbacks to this 
>approach?
>
>       -----Original Message----- 
>       From: flexcoders@yahoogroups.com on behalf of Tariq Ahmed 
>       Sent: Sat 7/23/2005 1:13 PM 
>       To: flexcoders@yahoogroups.com 
>       Cc: 
>       Subject: Re: [flexcoders] Flex and CFCs -- problems displaying 
> recordsets in datagrids
>       
>       
>        
>
>
>
>--
>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/
 


Reply via email to