IMHO, I think session, application, server variables
should be banished to the depths of hell.
I recently wrote an application using just the client,
variables, request and caller scopes. Gawd, talk
about making life easier!
Other than not allowing complex data types in client
variables, I would say the pros of client vars far
outweighs the cons.
--- "Tilbrook, Peter" <[EMAIL PROTECTED]>
wrote:
> <CFLOCK> is very important.
>
> ColdFusion is a multi-threaded application. Not
> locking writes to these
> variables could result in variable (memory)
> corruption.
>
> You should get into the habit of using CFLock even
> when simply
> outputting a applicatio, session variable.
>
> Ben Forta's excellent CF5WACK book -
> http://www.forta.com/books/0789725843/ explains
> locking in fine detail.
>
> Peter Tilbrook
> ColdFusion Applications Developer
> Australia New Zealand Food Authority
> Boeing House
> 55 Blackall Street
> BARTON ACT 2600
> Ph: +61-2-6271 2256
> Fax: +61-2-6271 2278
>
> http://www.anzfa.gov.au
>
> -----Original Message-----
> From: Gonzo Rock [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, 6 September 2001 2:45
> To: CF-Talk
> Subject: CFLOCK and Session variables
>
>
> A couple of questions that I can't
> seem to sort out from reading the DOCS...
>
> 1. Why would one need to use cflock when WRITING
> session.variables ?
>
> My impression is that:
>
> Session.var is NOT shared,
> Client.var is NOT shared,
> Application.var IS shared
>
> 2. Why would one need to use cflock when READING any
> shared variables?
>
> thanks y'all,
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
