On Tue, 12 Mar 2002 12:48:48 -0500, in cf-talk you wrote: >What would happen, for example, if your program received a value for >Form.myvar, and a different value for URL.myvar?
Dave, In my apps, the form variable would "win" the spot in the attributes scope. Not a problem. >My complaint with this technique is the same, essentially, as my complaint >with using the Request scope to share data between custom tags and their >calling pages. It breaks the model of defined inputs and outputs. I think those two issues are apples and oranges. In the case of the request scope and custom tags, I agree with you. A custom tag shouldn't be "reaching out" to grab its data from global variables... that data should be explicitly sent into the tag. But in the case of the formurl2attributes thing, nothing is breaking... attributes is as valid an input scope as form or url. There's no "reaching out" involved. -- Roger ______________________________________________________________________ Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation · $99/Month · Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusiona FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
