On 8 Oct 00, at 16:54, Stephen Garrett wrote:
> So the entire point is to make sure that you uniquely identify all
> request scope vars. I don't see that as a problem, this has been
> an issue for many systems over many operating systems for years.
Not really. It's a matter of knowing what's going on inside the black box.
For example, if you use a request-scope variable as the means to return a value
to a calling template, the author of the calling template must know to expect
the return value in that variable, regardless of what you name it. On the
other hand, if you construct the template to return the value to whatever
variable name the calling template specified in the calling attributes, the
author of the calling process gets to decide where the returned value gets
placed.
I guess I see it not so much as a matter of which approach is "right" as which
approach offers the most flexibility both in terms of the current application
and in terms of potential future re-use.
- Jeff
==============================================================
| Jeffrey S. Peters | "Specialization is for insects." |
| [EMAIL PROTECTED] | - Lazarus Long |
==============================================================
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
