Sorry - not very accurate with my first question. The user will have an option to persist the structure state using some sort of HCI event - button click - and then persist the structure.
Is this when <cfwddx> comes into play?
Yes it would be. Although I'm not sure what happens to a struct that is serialised/deserialised.
However, as Duncan said, how are you going to know when the session ends. Closing the browser or inactivity timeout will both leave the application with no trace that the session has ended.
What is it that you're actually trying to cache? Some kind of "shopping cart"?
Have you thought about using client variables (default 90days persistence) and a less complex data structure? With stuff like this I usually handle with simple lists in the form :
itemid | quantity | comment � itemid | quantity | comment
Its pretty painless and quick to convert the lists to/from an array or structure or use them as they are.
Hope that helps.
Regards
Stephen
-- These lists are syncronised with the CFDeveloper forum at http://forum.cfdeveloper.co.uk/ Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/
CFDeveloper Sponsors and contributors:-
*Hosting and support provided by CFMXhosting.co.uk* :: *ActivePDF provided by
activepdf.com*
*Forums provided by fusetalk.com* :: *ProWorkFlow provided by proworkflow.com*
*Tutorials provided by helmguru.com* :: *Lists hosted by gradwell.com*To unsubscribe, e-mail: [EMAIL PROTECTED]
