> My only problem with Request scope is that its available _everywhere_. I
> understand you can be a good developer and not use it in your model or
> elsewhere but I still dislike the request scope for that reason. Being a
> person that is constantly working on framework and components to be used i
>
> Err, how is it a 'pseudo-scope"? The request scope is a real scope
> (don't give it any confidence issues!) just as much as Variables. And
> I'll repeat my earlier assertion - that maybe seeing Request.Foo will
> help it stand out compared to Variables.goo.
;) You mis-read me (and I express b
My only problem with Request scope is that its available _everywhere_. I
understand you can be a good developer and not use it in your model or
elsewhere but I still dislike the request scope for that reason. Being a
person that is constantly working on framework and components to be used in
my com
> During our site rewrite, we opted to use the request scope
> over the variables scope for all "view" (CFM) pages. We use
> onRequestStart() to make sure certain global site variables
> are available in the request scope.
>
> After reading this article:
> http://www.schierberl.com/cfblog/inde
> > > In other words, do you use the variables scope at all on the "view"
> > > pages?
> > >
> > > Would you have used:
> > >
> > > ?
> >
> > If it's really a view page, in an MVC pattern, you wouldn't
> > have any CFQUERY tags in it.
>
> Of course, but that was just an example.
Yeah, that wa
Of course, but that was just an example.
m!ke
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]
Sent: Friday, May 23, 2008 1:44 PM
To: CF-Talk
Subject: RE: setting page variables in onRequestStart
> In other words, do you use the variables scope at all on the &q
> In other words, do you use the variables scope at all on the "view"
> pages?
>
> Would you have used:
>
> ?
If it's really a view page, in an MVC pattern, you wouldn't have any CFQUERY
tags in it.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
Fig Leaf Training: Adobe/Google/Pap
[mailto:[EMAIL PROTECTED]
Sent: Friday, May 23, 2008 10:23 AM
To: CF-Talk
Subject: Re: setting page variables in onRequestStart
During our site rewrite, we opted to use the request scope over the
variables scope for all "view" (CFM) pages. We use onRequestStart() to
make sure certain global sit
During our site rewrite, we opted to use the request scope over the variables
scope for all "view" (CFM) pages. We use onRequestStart() to make sure certain
global site variables are available in the request scope.
After reading this article:
http://www.schierberl.com/cfblog/index.cfm/2006/10/1
Err, how is it a 'pseudo-scope"? The request scope is a real scope
(don't give it any confidence issues!) just as much as Variables. And
I'll repeat my earlier assertion - that maybe seeing Request.Foo will
help it stand out compared to Variables.goo.
On Thu, May 22, 2008 at 8:21 PM, Dominic Watso
> variables.viewState?
Ok Mr Pedant, pick up on the useless bit of the post damn you
:p
--
Blog it up: http://fusion.dominicwatson.co.uk
~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to
date
Ge
variables.viewState?
On Thu, May 22, 2008 at 9:21 PM, Dominic Watson <
[EMAIL PROTECTED]> wrote:
> > 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 alwa
> 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.
Sure, I'd be with you usually; but this is an entire
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 PROT
> 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 varia
thanks Raymond
i haven't yet looked into the request scope but will do now!
thanks again
>Right, you can't do that. The variables scope in App.cfc isn't copied
>to the template.
>
>Unless you use onRequest. But that has some drawbacks as well.
>
>Why not simply simply use the Request scope?
>
>O
Right, you can't do that. The variables scope in App.cfc isn't copied
to the template.
Unless you use onRequest. But that has some drawbacks as well.
Why not simply simply use the Request scope?
On Thu, May 22, 2008 at 3:10 PM, Richard White <[EMAIL PROTECTED]> wrote:
> hi
>
> is it possible to
hi
is it possible to set page variables in the onRequestStart method of the
application.cfc?
if i enter the following code in the application.cfc:
and the following code in my page:
#myVariable#
i get an error message when running a page saying myVariable is not defined
~~
18 matches
Mail list logo
