You would still probably store the packet in the application scope - for all the reasons already mentioned.
-mk -----Original Message----- From: Dwayne Cole [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 27, 2002 10:46 AM To: CF-Talk Subject: Re: Re: WDDX in Session Variables > I think the general answer to that is. Why bother? Application and session > scopes can handle complex data types, only client variables can't handle > complex data. If you're accessing the navigation system on every page > request, then if you use WDDX you would have to initially serialise your > data, then de-serialise it for ever page request after that. Why not just > store it in a session or, if its the same for every user of the application, > in an application variable? I'm using javascript to build the display of the navigation system. So I deserialize the WDDX packet into javascript. Prof. Dwayne Cole MS in MIS, MBA Certified Advanced ColdFusion Developer 850-591-0212 "It can truely be said that nothing happens until there is vision. But it is equally true that a vision with no underlying sense of purpose, no calling, is just a good idea - all "sound and fury, signifiying nothing." The Fifth Discipline - Peter Senge ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
