Re: [flexcoders] Re: any disadvantages to using FDS + CF vs. FDS + Java?

[Tom Bray]

Thanks, Tom.  The primary responsibility of our server-side logic is to push data out to clients (updating user lists, sending validated chat messages, etc.), so it sounds like that's a deal-breaker for CF.  :(-Tom
On 7/5/06, Tom Jordahl <[EMAIL PROTECTED]> wrote:













  


    
            --- In flexcoders@yahoogroups.com, "Tom Bray" <[EMAIL PROTECTED]> wrote:

>
> Since we have more CF developers in-house, we're wondering if there
are any
> disadvantages or limitations of using CF with FDS instead of using Java.

Just wanted to jump in here and say that using ColdFusion does have
some advantages over Java.  For one thing, not having to write Java
code to do JDBC manipulation of your data is a big one.  We believe
that for RAD development, CFML (especially given the Flex Builder
wizards we provide)  will get you up and running much quicker.

A CF solution should scale very well, as you are offloading the
processing of the DB operations on to the CF server.  You do pay a
small price in moving the result sets from CF to Flex over a network
if CF and Flex are on different machines.

We fully support the change object model of writing Assemblers as
ColdFusion Components.  The one thing we do not support writing in
CFML is the 'server push' API which allows a Java application running
in the Flex web application to 'push' changes to the data in to the
Flex managed result sets.  We are currently evaluating supporting this
in a future release.

I hope this (biased) information helps.

--
Tom Jordahl
Adobe CF Team


      

    
    












__._,_.___





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



   Visit your group "flexcoders" on the web. 
   To unsubscribe from this group, send an email to: [EMAIL PROTECTED] 
   Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



  






__,_._,___