I'd argue that variables he is setting on - every- page request should be segregated for normal page variables. If I see request.siteURL for example, it flags it as a variable that is always available, as opposed to just 'X' for example.
On Thu, May 22, 2008 at 5:15 PM, Dominic Watson <[EMAIL PROTECTED]> wrote: >> Why not simply simply use the Request scope? > > Verbosity. The idea he is working on is doing something similar to the > way MG3 creates the 'helper scope' for udfs. I think helpers.myUdf() > is preferable to request.helpers.myUdf() though its all good. Clearly > with MG, the helper/event/viewstate variables are setup outside of any > cfcs and I hadn't figured that in the sample code I came up with (I > still use application.cfm). > > Dominic -- =========================================================================== Raymond Camden, VP of Software Dev, Broadchoice Email : [EMAIL PROTECTED] Blog : www.coldfusionjedi.com AOL IM : cfjedimaster Keep up to date with the community: http://www.coldfusionbloggers.org ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;192386516;25150098;k Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:305930 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
