I just thought I'd share this truly demented idea on I had on maintaining synchronization on clusters before I learned that Databases can do it much easier. Before I knew databases could track application and session variables, I had to ask "how to maintain sync between servers?" My answer would have been a piece of code plugged into all my apps that could have 1) Caught a "session variable not found" exception generated by the server if such was generated 2) Use CFHTTP to grab app and session variables from the other servers in the cluster until it found the ones it liked. 3) Then looped through the registry via CFREGISTRY to update the app and session variables. Now anybody could have seen some of the problems here: 1) the dreaded CFREGISTRY tag is being used on a front end web server, I hope I'm not giving any hackers a backdoor 2) what would happen if the CFLOOP over the CFREGISTRY went infinite, now granted a few of us have seen the sickening results when CFLOOP goes infinite over CFMAIL, does anyone wanna clean out a few million CFID entries from the registry? Any volunteers? I thought so.... Gregory Harris Los Angeles ITA Dept. [EMAIL PROTECTED] ------------------------------------------------------------------------------ Archives: http://www.mail-archive.com/[email protected]/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebarRsts&bodyRsts/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
