I have an intranet application which has 100-200 concurrent users at peak
times during the day.  The application uses a fairly large number of session
variables.  Early after the application went to production, I had a large
number of users who were assuming the cfid and cftoken values of other
users.  After locking every session level write statement exclusively and
every session level read statement read-only, the problem has been reduced,
but not eliminated.  While I am not sure that I have locked the variables in
the most efficient manner, I believe that all session variables have been
locked.  Any ideas on where else to look for a solution to this annoying
situation?

In a possibly related question, what is best practice for passing the cfid
and cftoken around the application?  I am currently using a cfparam tag to
set session.addtoken= "cfid=#client.cfid#&cftoken=#client.cftoken#"  in the
appGlobals (fusebox) template.  I then append "#session.addtoken#" to the
url string throughout the app.

Thanks for any input.

David

------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
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.

Reply via email to