enforce locking on application and session
variables. You just need to put a CFLOCK around your CFSET's.
Silly. We already did that. You didn't read past the error message!
Actually, the question was, has it always been a problem to lock
Application variables and Session variables
or Solaris (and had already been
live load tested without a problem). Has it always been a problem locking
application and session variables in the same lock or is this new to 4.5?
--
Archives: http://www.eGroups.com/li
2 matches
Mail list logo