To stay on topic, and most likely cause more trouble, I on the other hand would like <cflock> to go away and not be necessary for session, application or server variables. It is my firm belief that variable locking should be part of the core CF engine and not part of the higher level scripting language. Especially since it appears to always be required. As much as I understand the reasons for it's current existence in a multi-threaded environment, <cflock> still has the appearance of being a patch to a design flaw.
Best regards, Dennis Powers UXB Internet - A Web Design and Hosting Company tel: (203)879-2844 fax: (203)879-6254 http://www.uxbinternet.com/ http://dennis.uxb.net/ -----Original Message----- From: David Schmidt [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 30, 2002 12:42 PM To: CF-Talk Subject: CF Wishlist Ok, Have carefully considered what I want from CF, the most striking feature I want to see is... "Stop treating empty list items as null." That is a list of "3,5,,,3,2,2" should have a length of 7, instead of 5. Doing this would nearly eliminate the need for any field names like name="cost_#i#", since HTML sends back "3,5,,,3,2,2" for duplicate text fields named "cost" anyways. ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com 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
