Once again, Dave Watts proves to be right.   Do you ever get sick of
being right, Dave?

Turns out you can serialise a CFC using java (which is why i couldnt
find it in the docs).   Using the technique outlined in teh blog at
http://www.rakshith.net/blog/?p=4

It takes a CFC, which can be a very seriously complex variable, and
turns it into a string.  Once as a string it can be written to a file,
stored in a database, emailed,  lots of stuff could happen to it.

Using java, the opposite is also true.   You feed a java function the
serialised CfC in the form of the string (which could have been pulled
out of a database or read in from a file, even a SMS message i
suppose)  and reconstituted into the CFC again for use elsewhere.

Neat.  And that's exactly what we were looking for for this project.
It means instead of tinkering with the existing code, and patching
more patches on the patches, we're going to start again from scratch
and build a new site.   We can discard all the legacy inefficiencies
and do the job properly using new techniques!

Thanks!

Cheers
Mike Kear
Windsor, NSW, Australia
Adobe Certified Advanced ColdFusion Developer
AFP Webworks
http://afpwebworks.com
ColdFusion, PHP, ASP, ASP.NET hosting from AUD$15/month



On 12/13/07, Vince Bonfanti <[EMAIL PROTECTED]> wrote:
> Even if CF8 can serialize CFCs (I've read that it can), I don't think you can 
> store complex variables in the Client scope. I'd assume that a serialized CFC 
> would be considered a complex variable.
>
> Vince Bonfanti
> New Atlanta Communications, LLC
>
>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
ColdFusion 8 - Build next generation apps
today, with easy PDF and Ajax features - download now
http://download.macromedia.com/pub/labs/coldfusion/cf8_beta_whatsnew_052907.pdf

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:294612
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4

Reply via email to