What type of structured data? The only thing you need to pass is XML. A CFML Struct can be serialized into a XMLDocument, and the same counts for Arrays, Lists, Queries, etc. you name it.
Maybe I am missing the entire idea behind your goals :) 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: Jim Davis [mailto:[EMAIL PROTECTED] Sent: dinsdag 16 augustus 2005 15:22 To: CF-Talk Subject: RE: Ajax and CFCs > -----Original Message----- > From: Thomas Chiverton [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 16, 2005 7:28 AM > To: CF-Talk > Subject: Re: Ajax and CFCs > > On Monday 15 August 2005 20:12, Jim Davis wrote: > > 2) Passing structured data once you access them. > > It's the second bit that gets confusing as hell. > > It's trival to write toXML() methods on all your objects. > MM even have a query2xml on DevNet. People that say things are "trivial" annoy me. ;^P It IS trivial on the server-side - not so trivial on the client side. Also it's trivial to write _A_ packet on the server and _A_ consumer on the client for that one packet... but as you build more and more one-offs it gets less and less "trivial". Again (and again and again) what we really need is a decent client-side parser for common formats. The only truly common format right now is SOAP-based web services (although they're still flaky as hell). IF you had such a library, completely client-side, you could instantly (in theory) consume web services from nearly all major server-side packages - most with little to now extra coding. What we really need is a rich, client-implementable _standard_ for transmission of structured data over HTTP. Something that (I think) needs to be a little more complex than JSON but not as complex as SOAP. Something like WDDX could have fit well... but it seems to have withered on the vine. Jim Davis ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:215216 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
