Thanks Tom. Like João, I am interested in the mechanics of track
changes/sync/persist process.

You asked "How do you envision a CFC backend to Flex2 Data services?". I am
hoping that FDS will allow multiple approaches to a CFC backend as, as we
all know, there is no one method or framework for writing a persistence
layer in CF.

For example if you take a look at the FDS section of Christophe Coenraets'
FES overview, here:

http://labs.macromedia.com/wiki/index.php/Flex_Enterprise_Services:overview#
Flex_Data_Service_2

It is very easy to imagine the backend CF code that could be used instead of
the java code in his example, i.e. in flex-services.xml

<destination id="contact">
   <adapter ref="CF-DAO"/>
   <properties>
       <metadata>
           <identity property="contactId"/>
       </metadata>
       <server>
           <assembler>
               <class>PATH.TO.MY.DAO.CFC</class>
               <singleton>true</singleton>
           </assembler>
           <fill-method>
               <name>loadContact</name>
           </fill-method>
           <sync-method>
               <name>syncContacts</name>
           </sync-method>
       </server>
   </properties>
</destination>

Just two changes, and then instead of a ContactAssembler java class you have
a CFC containing the various methods (fill, sync, etc); and within each of
these methods you could have either simple persistence code (e.g. direct
cfquery calls) or more complex code such as integration with your
persistence framework of choice (e.g. Reactor/ARF). Even the sync method is
straightforward as after all we used to have to do this sort of thing when
handling the multiple changes from the old CFGRID java applet.

As I said, it is easy to imagine basic persistence BUT what is harder to
envisage are the things João mentions and others. For example;

- Complex data objects & nested destinations

- What do we need to do on the CF/data side to help FDS keep track of
changes/dirty records (e.g.. do we need to make sure all CFC instances have
a 'dirty' attribute or do we need to have a modified date on the database
record.

- How do we notify FDS of outside data changes, for example from other
presentation layers perhaps, but not necessarily, using the same CFC
persistence layer, within or without a framework (e.g. ModelGlue). Perhaps
by FMS and CF event gateways?

- How will paging work

- The usual type casting issues

All of the above, I imagine, need to be tackled for all of the other FDS
adapters too.

Thanks again Tom, any further information is gratefully received.

One last thing - I do think it is very important that when Flex 2 and/or
Enterprise Services is finally released, that it include a CF FDS adapter.
Not only is it important to us Cfers but I think it also sends a wider
message that Adobe is beginning to exploit the synergies between products
(Flex & CF) in its portfolio.

Regards
Ian


-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On
Behalf Of Tom Jordahl
Sent: 05 January 2006 18:35
To: [email protected]
Subject: SPAM-LOW: [flexcoders] Re: Beta Flex 2 release Date? Any one for a
Guess

Hello,

I am working on the ColdFusion MX 7 and Flex2 integration.  Here is what we
currently have scheduled to be available around the same time as the next
Flex2 beta.

- An update to the CFC Adapter that is currently available on Macromedia
labs.  This is mainly bug fixes, and updates to stay in sync with the
current Flex2 code.

- A CF Event Gateway Adapter for Flex2 and Flex Asynchronous Event Gateway
for CFMX7.  These two pieces together allow you to publish and subscribe to
Flex Enterprise Services "destinations" from a ColdFusion Component.  You
can publish messages from a Flex client that a CFC will receive.  You can
publish messages from CFML code that a Flex client can see.  For an idea on
how this can be used, see the Flex JMS (Java Messaging Service) Adapter
example.  This is for Async Messaging and does not integrate ColdFusion with
Flex Data Services (see below).

So the major new piece here is integration with the publish/subscribe
functionality in the Flex2 Messaging services.

We are also looking to create an adapter that will enable a ColdFusion
Component to be the back end to the Flex Data Services layer, similar to the
way Java Objects can currently be used.  I don't expect this to be available
at the same time as the next beta, but miracles can happen. :)  Rest assured
that we want to get this kind of functionality into your hands and get as
much feedback on it as we can.

FYI, we also are hard at work on some CF-specific Flex Builder 2
productivity extensions that should dramatically increase the productivity
of RIA construction for CF customers, and make the leap to RIA development
for CF customers new to RIA with Flex2 a super easy, fun and productive
experience, but more on that later :)  

Questions:
- Do you think you can use the pub/sub functionality as described?
- How do you envision a CFC backend to Flex2 Data services?

--
Tom Jordahl
Adobe ColdFusion Architect




--- In [email protected], Vinny Timmermans <[EMAIL PROTECTED]>
wrote:
>
> Hi David,
>  
> I am working on an Flex 2 /CFMX7 Enterprise project and my main
concern at
> the moment is whether the Flex Enterprise Gateway beta for CF,
announced at
> MAX, will be released at the same time as the Flex Enterprise
Services beta.
> In other words, can we get our hands dirty connecting the new Flex 2 
> Dataservices with CFMX 7 Enterprise in a straightforward way in 3-5
weeks? 
>  
> Best,
>  
> Vinny
> 
> 
>   _____
> 
> From: [email protected] [mailto:[EMAIL PROTECTED] 
> On Behalf Of David Mendels
> Sent: woensdag 4 januari 2006 22:15
> To: [email protected]
> Subject: RE: [flexcoders] Beta Flex 2 release Date? Any one for a 
> Guess
> 
> 
> Hi all,
>  
> Good to hear you are eager.  The team is hard at work.  The next
beta will
> be a big leap forward.  I am not going to give a specific date or
commit to
> anything...we need to make sure the beta is ready before we ship it,
but I
> would expect it in 3-5 weeks. NO guarantee.
>  
> In the meantime, I'd love to hear more about what kinds of projects
you are
> working on for Flex 2, were you using Flex 1.X or is this your first
Flex
> project, nature of team, high level impressions, concerns, etc.
>  
> Regards,
> David
> Adobe
> 
> 
>   _____
> 
> From: [email protected] [mailto:[EMAIL PROTECTED] 
> On Behalf Of Jose (DSM) Lora
> Sent: Wednesday, January 04, 2006 3:34 PM
> To: [email protected]
> Subject: RE: [flexcoders] Beta Flex 2 release Date? Any one for a 
> Guess
> 
> 
> 
> Same here, I have a development team waiting for that Beta
> 
>  
> 
> 
>   _____
> 
> 
> From: [email protected] [mailto:[EMAIL PROTECTED] 
> On Behalf Of sufibaba
> Sent: Wednesday, January 04, 2006 2:15 PM
> To: [email protected]
> Subject: [flexcoders] Beta Flex 2 release Date? Any one for a Guess
> 
>  
> 
> Hi All,
> 
> Can anyone give an estimate on when Flex 2 will be released?  It 
> doesn't have to be a final word, just an approximate time.  We are 
> working on a Flex 2 project that is being slowed to a halt do the many 
> bugs in Flex Alpha.
> 
> Sincerely,
> 
> Tim





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