It's for a multilingual site. Every bit of text on every page (every button, label,
alt, and open text) has been replaced by:
#label.labelname#
An Application scope structure has been set up in Application.cfm (from a database
query) to pre-load all the text in all the languages once only. Dur
> 1. It's going to reside in memory one way or the other.
> Either one copy as an Application variable or one copy for
> each page request currently executing as a "variable"
> variable or a request variable. This isn't idle curiosity for
> me, I am doing this on a site that has almost a thous
1. It's going to reside in memory one way or the other. Either one copy as an
Application variable or one copy for each page request currently executing as a
"variable" variable or a request variable. This isn't idle curiosity for me, I am
doing this on a site that has almost a thousand "consta
> Why wouldn't he put it in an Application variable? If it's
> the same for everyone that would make the most sense to me.
>
>
>
>
>
>
>
> If you never EVER EVER set it anywhere else, you shouldn't
> need to lock it for reads, would you?
Two points.
1. If the variable's never g
Why wouldn't he put it in an Application variable? If it's the same for everyone that
would make the most sense to me.
If you never EVER EVER set it anywhere else, you shouldn't need to lock it for reads,
would you?
At 04:45 PM 8/29/00 -0400, Dave Watts wrote:
>> In my applicati
> So I don't need to lock application-scope variables? One book
> I have says I should. How about request-scope vars?
If it's a memory variable, you need to lock it. If it's not, you don't.
However, setting a variable in application.cfm doesn't make it an
Application variable. Instead, it's a lo
rth <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 29, 2000 3:49 PM
Subject: Re: CFLOCK datasource var?
> You shouldn't need to use a Session variable for your DSN .. especially if
> you are going to be setting it over and over in your Application.cfm.
That
> Yeah, but the "Variables" scope isn't persistent. Each time
> a page loads it will unset itself. It would be better IMHO
> to just do a plain vanilla CFSET.
When you do a "plain vanilla" CFSET, you're using the Variables scope. If
you set a local variable (one within the Variables scope) in
a
> > It's new to CF 4.5.x. It's similar to the local Variables scope
>
> Actually it was in CF 4.01. (And no, I don't mean to be nitpicky,
> but I know a lot of people still use 4.01, so I didn't want anyone
> to think they couldn't use it. :)
No, you're not being nitpicky at all. Better to sta
> -Original Message-
> From: Dave Watts [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 29, 2000 5:04 PM
> To: '[EMAIL PROTECTED]'
> Cc: '[EMAIL PROTECTED]'
> Subject: RE: CFLOCK datasource var?
>
>
> > I'm unfamiliar with the r
.563.5559 x 228 Voice
704.849.9291 Fax
-Original Message-
From: Todd Ashworth <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tuesday, August 29, 2000 4:48 PM
Subject: Re: CFLOCK datasource var?
>You shouldn't need to use a Session variable for your
> I'm unfamiliar with the request scope and can't seem to find
> it in any of my docs. Where is a request-scope var stored?
It's new to CF 4.5.x. It's similar to the local Variables scope in that it's
stored in memory until the entire page has been generated, then it's
discarded. The advantage o
t;[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, August 29, 2000 3:45 PM
Subject: RE: CFLOCK datasource var?
> > In my application.cfm I set a session var for all my queries'
> > datasource like this:
> >
> >
> >
, you
wouldn't have to worry about locking at all.
Todd Ashworth
- Original Message -
From: "Ricq Pattay" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 29, 2000 4:42 PM
Subject: CFLOCK datasource var?
| In my application.cfm I set
> In my application.cfm I set a session var for all my queries'
> datasource like this:
>
>
>
>
>
> So... Do I need to read-only lock every reference to
> session.ds in all my other templates where I have a query
> using that datasource session var? e.g.,
>
>
> select sysdate from dual
In my application.cfm I set a session var for all my queries' datasource
like this:
So... Do I need to read-only lock every reference to session.ds in all my
other templates where I have a query using that datasource session var?
e.g.,
select sysdate from dual
Since session.ds is always
16 matches
Mail list logo
