1.) WDDX packet immediately gets too big for the URL.Real fast.
2.) Having the old info in the packet is what's gonna pre-fill the form with
their previous choices. This is a good thing. You can place an "Erase Form"
button on your page that will dump their packet before reloading the page.
Alan McCollough
Web Programmer
Allaire Certified ColdFusion Developer
Alaska Native Medical Center
> -----Original Message-----
> From: Brad Roberts [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, January 19, 2001 11:13 AM
> To: Fusebox
> Subject: cflocation, form variables, wddx packet, blah blah
>
> I've got something similar that I just ran into (concerning cflocating and
> form variables).
>
> I wrote a tag to look for certain 'attributes' scoped variables and put
> then
> into a wddx packet. I want to be able to just pass around the wddx packet
> from form to form or page to page, and not have to pass the variables
> individually in hidden fields.
>
> Does anyone have a "best practice" for this? Do's, don'ts, etc.?
>
> Here are some questions and problems I've run into:
>
> 1.) Can a wddx packet get too large to pass via url?
> 2.) I tried storing the wddx packet as a client var, but if the user goes
> back and chooses different search criteria, it may be possible that some
> of
> the old criteria is left in the packet, thus giving incorrect search
> results.
>
>
> Brad
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
