<cflock scope="session" timeout="30" type="exclusive"> <cfset session.variable = blah> </cflock>
Use type="exclusive" for writing to session variables, then use type="readonly" for reading from them. ______________________ steve oliver cresco technologies, inc. http://www.crescotech.com -----Original Message----- From: han peng [mailto:[EMAIL PROTECTED]] Sent: Monday, January 28, 2002 8:43 PM To: CF-Talk Subject: Re: multi-page forms hihi... juz curious.. wat do u mean by locking the session variables..?? how do u do it..? any examples..?? thanx han ----- Original Message ----- From: "David Hannum (Ohio University)" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Tuesday, January 29, 2002 8:38 AM Subject: Re: multi-page forms > Option B baby. Just lock 'em. > > Dave > > > ----- Original Message ----- > From: "Cornillon, Matthieu" <[EMAIL PROTECTED]> > To: "CF-Talk" <[EMAIL PROTECTED]> > Sent: Monday, January 28, 2002 5:49 PM > Subject: multi-page forms > > > > Hi. I am building a login/registration system for the Intranet site that > I > > manage. In order to collect user data from new users, I am creating a > > multi-page form. I am breaking into multiple pages to make it less > > overwhelming for the user. But this introduces the issue of passing > > variables from page to page. I see several options open to me, but I was > > wondering whether there were any thoughts out there (I'm sure there are > > plenty!) as to which is the best option, what pitfalls may exist, etc. > What > > most concerns me is the likely-to-be-very-common occurrence of users > backing > > up through the process to revise data. I am concerned that it will be a > > major headache to keep track of things when there are so many options for > > how the user might get to each page (e.g., "got to page 2 by submitting > page > > 1" or "got to page 2 by clicking back button on page 3", etc.) > > > > The options I see: > > > > A) Pass all variables through forms from page to page, using hidden > > variables on page 2 to pass the variables from page 1, etc. Variables > from > > each page would be validated as the first step of the next page. At the > end > > of the multi-page form, all of these accumulated variables are written to > > the SQL database. > > > > B) Each page's submit button sends the form to an action page which > > validates the data, puts it in session variables, and sends the user on to > > the next page. At the end of the multi-page form, the values of the > session > > variables are passed to the database. > > > > C) Like option B, but variables are written to temporary SQL table record > > instead of to temporary session variable. > > > > Thoughts? > > > > Thanks, > > > ______________________________________________________________________ Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusiona 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
