It seems to me that the various scopes can be loosely grouped... FORM, URL and ATTRIBUTES are fundamentally different to other scopes. They are the three scopes where we pass parameters. The main difference between the three scopes is the SOURCE of the parameter. As we want to promote re-use, we don't want our code to care about the source of the parameter, so we roll the three scopes into one. I'd like to see this addressed by Allaire, perhaps, with a new PARAMETER scope. In the meantime, we have FORMURL2ATTRIBUTES. Problems with FORMURL2ATTRIBUTES: - If it's true that this doesn't create "true" ATT scope vars, is that a terrible problem? Can we write code to loop through variables named "attributes.*"? - Performance. We need some benchmarking. You'd have to convince me that the perf hit was significant compared to normal webby-bandwidth problems, in order to justify dropping FORMURL2ATTRIBUTES. - Typing. Customize your editor. - Security. Has someone mentioned this one? Automatically turning URL parameters into ATTRIBUTES can be dangerous if you're not careful. More thoughts? lee IMPORTANT NOTICE: This e-mail and any attachment to it is intended only to be read or used by the named addressee. It is confidential and may contain legally privileged information. No confidentiality or privilege is waived or lost by any mistaken transmission to you. If you receive this e-mail in error, please immediately delete it from your system and notify the sender. You must not disclose, copy or use any part of this e-mail if you are not the intended recipient. The RTA is not responsible for any unauthorised alterations to this e-mail or attachment to it. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
