CFHOUR() Q/A Show - What does X really do?
Jun 30
posted by Dave in
Q/A Series, CFHour.com
| 1 Comments
Here we go again. Round 2 in the CFHOUR.com Q/A show series. The first time we did this we had such a large response it spanned 2 shows.
This time we want to answer your questions on "What does X really do?". Now, X can be anything (ColdFusion / Technology related of course). Anything from, the CFQUERY tag to a setting in the cf administrator. No question is to small or large.
Yea, you could probably find your own answer in the ColdFusion docs. However, the docs do not give real world, practical answers. We will lean on our experience and give you the answers that you just cant find in the help docs.
Send in the questions.
Till next time...
--Dave
#1 by Jose Galdamez on 7/23/09 - 1:15 PM
I found myself trying it out a couple of weeks ago when I needed to pass a query object from one page to another. Storing it in the Session scope was probably the easiest and most efficient solution, but I thought I'd give the WDDX approach a try.
I really didn't have too much success. I tried passing it via a hidden form input tag, and later a hidden textarea field. In both cases, the receiving page did not recognize the passed form field as valid WDDX, so I couldn't convert the WDDX back to CF. With the code being verbose as it was, I didn't even want to risk passing it via a URL parameter (isn't there a limit on URL parameter length?).
After enough tries, I went back using the Session scope.
So that's essentially the back story. I'm just curious if there are any other scenarios where WDDX may be more useful, such as storing complex variables in cookies, databases, etc.
Personally, I'd be weary of storing WDDX in cookies cause cookies are supposed to have file size limits. What those file size limits are I don't know. I just wouldn't expect them to be much.