-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 IT strikes me that possibly the confusion stems not so much from understanding the request scope, but from not understanding the ways that fusebox apps can be integrated and thus the ways that the request scope could get overwritten for a particular user. I've never had the need to incorporate a third party fusebox app and actually little chance to reuse my code. The idea of calling a fusebox app as a custom tag or how integration of multiple apps might work is confusing to me (and others). But I suspect that this is exactly the area that the request scope really becomes a problem. The problem with variables of the same name getting overwritten during a particular request would seem to exist with other scopes as well. The problem really seems to be that the request scope goes so far as to overwrite variables coming from custom tags. There also seems to be some semantic confusion since my understanding is that the request scope is limited to an individual request, but not an individual user, even though these are effectively the same thing, aren't they, since a single request can't be shared... c -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8ckt - http://irfaiad.virtualave.net/ Comment: PGP Signed for message verification and/or encryption Comment: KeyID: 0xD68B61E851046CFD iQA/AwUBOeSPytaLYehRBGz9EQLK/gCgnxpScufUz7d4lbTPRsKqyL3TXVAAoPE0 5tyzywYbQSub525jw7jk07nl =qy8F -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ 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.
