Are there requirements for such changes (Ajax<>Flash), if not, is this not a clear example of phantom requirements?
I personally would not use a CFC in a web service model for supplying the interface with data. I'd rather use a specialized presentation layer providing formatted datasets in a XML stream. This is a far more lightweight solution than SOAP envelopes, and allows future use of a different specialized presentation layer to accommodate different platforms. This specialized layer is also responsible for initially handling post requests. But as I always say, do you want to create widgets following the Ajax design pattern, or do you want to deliver fully blown dynamic interfaces where you limit the chances of hitting a postback event. If it is the latter, expect some heavy studying in all sorts of web technologies and a lot of practice. Many people like to talk about it but those who actually do can be counted on one hand. At least, try to avoid injecting complete code. Try setting up a framework around DOM methods. :) Micha Schopman Project Manager Modern Media, Databankweg 12 M, 3821 AL Amersfoort Tel 033-4535377, Fax 033-4535388 KvK Amersfoort 39081679, Rabo 39.48.05.380 ------------------------------------------------------------------------ ------------------------------------------------------------------------ ----- Modern Media, Making You Interact Smarter. Onze oplossingen verbeteren de interactie met uw doelgroep. Wilt u meer omzet, lagere kosten of een beter service niveau? Voor meer informatie zie www.modernmedia.nl ------------------------------------------------------------------------ ------------------------------------------------------------------------ ----- -----Original Message----- From: wolf2k5 [mailto:[EMAIL PROTECTED] Sent: dinsdag 16 augustus 2005 11:48 To: CF-Talk Subject: Re: Ajax and CFCs On 8/16/05, Micha Schopman <[EMAIL PROTECTED]> wrote: > Just wondering, why would you want to communicate with SOAP envelopes in > the first place? If you are exchanging data with such complex structures > it is clearly a case of the wrong approach towards the Ajax pattern. My plan it to do as little as possible server-side code changes for the AJAX interface. Since my application already uses CFCs, it would be great to re-use the same methods for the AJAX interface. Do you mean that I should avoid complex structures in my AJAX interface? I know that SOAP has some overhead over plain XML data, but I think that the advantage of reusing the same code is a winner here. Please let me know if I am missing something that will prevent me from doing that. Thanks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:215148 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
