Problem #2 happens all the time with session or application variables. Many
developers put them into local scope once with <cflock> to use them. You
don't want to be locking and unlocking every time you need a value from a
session or application variable. This all might be moot in CF 5.0. I'm not
up on new features.
---
Jeffrey B. Marsh
Professionals built the Titanic.
Amateurs built the Ark.
-----Original Message-----
From: Jeff Peters [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 23, 2001 9:47 AM
To: Fusebox
Subject: Re: Musings on Attributes (was Best Practices...)
On 23 Mar 2001, at 11:04, Steve Nelson wrote:
> Let me bring up the question again.... What problem are we trying to
> solve?
My tests tell me there's no real performance hit with formurl2attributes, so
I
see the problem in two parts:
1. The "attributes" scope as generated by formurl2attributes isn't the
Attributes scope, so you can't do loop operations over an attributes
structure
and see all form, url, and attributes variables.
2. Formurl2attributes creates copies of form and url variables, thus
doubling
the server memory used for those scopes in Fusebox apps. I'd much rather
see a
means to use a structure of pointers that would cover form-, url-, and
attributes-scoped variables. This would accomplish the same goals as using
the
current approach, while streamlining memory use and providing a complete
structure for accessing variables "passed into" a Fusebox module.
That's the problem I'd like to solve. It's not a showstopper, but it has
important implications.
- Jeff
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
