Pete,
In this specific case we needed to keep track of a form's input with
possibly several *hundred* fields - allowing the user to save the data
locally as HTML, print it and more... all of this without saving it on our
server (legal issues).
With WDDX you can pack a complex variable - a structure with values, arrays
and other structures - all into a string which then can be kept in a hidden
form field to be passed back to the server when the form is submitted.
Another neat thing is if you use JavaScript you can pack a whole form's data
into an object then serialise it into WDDX on the client and submit to the
server one field with the WDDX then on the server you get the data in the
exact same structure - very useful if you have a variable number of sections
on the form - or several repeating sections.
Regards,
Noam
----------
From: Peter Lutwyche [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, 30 January 2001 11:22
To: Fusebox
Subject: RE: (not really) db client vars and multiple instances
Noam,
Do you have an example of how you would use a "hidden WDDX form
field"? What advantage would this confer over an ordinary hidden form field?
I'd be grateful for any insight - sounds real interesting and might
just help solve a current problem.
Pete.
>>> BOROVOY Noam <[EMAIL PROTECTED]> 30 January 2001 09:24:38
>>>
>>> My fix for this is as follows:
>>> 1. avoid as much as possible persistent data and pass the data
back and
>>> forth to the client on the url or as hidden wddx form fields
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
