> Which is more readable?
>
> #createTimeSpan(0, 0, 0, 10)#
> 0.000115741
>
> Sure, the execution time is slightly less for the latter, but
> if you care about that last few microseconds, I'd highly
> recommend dumping CF for assembler. The beauty of CF is that
> it's really easy to learn, co
barneyb
> -Original Message-
> From: Thomas Chiverton [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 23, 2004 8:29 AM
> To: CF-Talk
> Subject: Re: Application vs Request scope
>
> On Friday 23 Apr 2004 16:17 pm, Matt Robertson wrote:
> > cachedwithin="
Thomas Chiverton wrote:
>you can put a fractional day here, rather than doing a
>createTimeSpan() for every page request.
Yes, ever since Michael posted that on HoF I've been doing it, and it
makes a lot of sense. I still use CreateTimeSpan when I plug in
parameters instead of hardcoding the exp
On Friday 23 Apr 2004 16:17 pm, Matt Robertson wrote:
> cachedwithin="#CreateTimeSpan(0,0,0,10)#">
Just a quickie, but you can put a fractional day here, rather than doing a
createTimeSpan() for every page request.
cfdump a createTimeSpan call to see what I mean.
--
Tom Chiverton
Advanced Col
p.s. leave that silly maxrows statement out.
--Matt--
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
Spectrum Web Design wrote:
>Hi Matt. Do you can share this technique about
>store application/request vars in DB ? Interesting...
Sure, but given CF 6+'s handling of shared memory vars, I wouldn't
consider this unless you are on CF 5 or need to be compatible with it.
Anyway...
I have a table nam
Hi Matt. Do you can share this technique about store application/request vars in DB ? Interesting...
> I use request scope. Declaration is short and simple. No resource
> drain noticeable.
>
> Are all shared scope reads safe to no lock now? I thought it was only
> session var reads that were
On CF 5 and below I use the request scope. No locking is required, but you
do have multiple copies of the same information using resources (although no
more copies than allowable threads on the server). For large data sets or
data which takes a while to fetch (queries) I use the Application scope
ll is before the cfc's init() method is
called. Legal, but usually not what you want at all.
Cheers,
barneyb
> -Original Message-
> From: Chris Alvarado [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 22, 2004 2:12 PM
> To: CF-Talk
> Subject: RE: Application vs
Chris Alvarado wrote:
> Can you please describe a race condition to me?
>
> I know what it means conceptually, basically when you have one thing
> that needs to happen before another an not simultaneously, but I cant
> really think of an instance where this would be the case.
Imagine the foloowin
22, 2004 2:08 PM
> To: CF-Talk
> Subject: RE: Application vs Request scope
>
> Barney Boisvert wrote:
> >In CFMX, everything is completely safe to use without any locking.
> >You only ever need to lock for race conditions.
>
> *everything* as in reads AND write
developer ]
4 Guys Interactive, Inc.
281.807.4344 x1716
_
From: Barney Boisvert [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 22, 2004 3:57 PM
To: CF-Talk
Subject: RE: Application vs Request scope
> Are all shared scope reads safe to no lock now? I thought it
> was only sessi
Barney Boisvert wrote:
>In CFMX, everything is completely safe to use without any locking.
>You only ever need to lock for race conditions.
*everything* as in reads AND writes? I could have sworn the rule was reads only.
OMIGOD I helped propagate another locking thread. There's only one hono
> Are all shared scope reads safe to no lock now? I thought it
> was only session var reads that were completely safe.
>
No, im MX they are all safe - you only have to worry about race conditions.
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
u know exactly when you have to
flush, and you never flush when it's not needed.
Cheers,
barneyb
> -Original Message-
> From: Matt Robertson [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 22, 2004 1:48 PM
> To: CF-Talk
> Subject: Re: Application vs Request scope
>
I use request scope. Declaration is short and simple. No resource drain noticeable.
Are all shared scope reads safe to no lock now? I thought it was only session var reads that were completely safe.
Another thing I use a lot of is a cached db query. I'll have a table with a structure that has
16 matches
Mail list logo
