Folks,
I have an application that presents its users with a page of survey
questions -- a page that is built by a CF template that consults a database.
As part of building the page, the template places data about each question
it places on a page into a structure and then places that structure into an
array. The questions are placed on the page inside a CFFORM. The action
template for the form consults the array of structures to determine how to
interpret the filled in answers to the questions.
Until now (we are still in development), the array of structures has been
kept in session scope variables. After each page of questions is processed
by the action template, the array and its contained structures is
reinitialized. There will never be more than about 15 questions on a page so
it is easy to calculate the maximum memory usage for session variables.
But now we have a scalability problem. I need to add features to allow the
user to press the Back button to return to an earlier page and begin again
from there. My (tentative) solution is to not reinitialize my array of
structures but store each into a more overriding array of pages.
Now I begin to worry about memory usage inherent in session scope variables
and would like to switch to client scope variables stored in a database.
But it appears that client variables must be scalar and can't be arrays or
structures. Is that true? It doesn't explicitly say so in the Allaire
manuals or the Forta books, but I got an error for CF when I tried to store
an array into a client variable. If so, how can I get around it?
Any advice will be appreciated. How do I make a fairly large amount of
structured data persist for the life of a session without using up too much
server memory?
Thanks, for any light you can shed on this for me.
-- Tim Dempsey
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
