cheer 100-200 application scoped variables, that a lot :-) are they all read/written frequently... whats your apps performance like?
-----Original Message----- From: Douglas Humphris [mailto:Douglas.Humphris@;unitech.net] Sent: 31 October 2002 09:56 To: [EMAIL PROTECTED] Subject: [ cf-dev ] Config best practice I was having a chat with a colleague yesterday about whether we should be storing our configuration variables in a cfm file which is included in Application.cfm and stored in the db and cache the query call from Application.cfm. My gut feeling is to follow Sean Corfield's best practices recommendation: http://www.corfield.org/coldfusion/codingStandards.htm#Anchor34 ie use the included file with variables set in the request scope. However, the application we're working on currently uses something in the region of 100-200 application scoped variables. We're looking to transfer all those into either the request scope or a cached recordset so as to avoid locking. The cached recordset would probably provide better performance but is it good practice? The app currently supports CF4.5+ though we're hoping to move it out of the dark ages soon if we can put a strong enough case to our clients to move to CFMX. I was just wondering what people are doing with their global variables. What do you recommend? Cheers Doug -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
