Yeah, like you said. I goofed. No need to cflock client vars - the db will
probably do it for you.

Nat Papovich
ICQ 32676414
"If it was hard to write," 
says the Real Programmer,
"it should be hard to understand."


-----Original Message-----
From: McCollough, Alan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 11, 2000 9:37 AM
To: Fusebox
Subject: RE: Idea? (Don't read it Marc.) 


Okay, now I gotta jump in. I'm a die-hard user of database-driven client
vars. Now, as far as db-driven client vars go, aren't they implicitly
locked, since a read of a client var is a specific SELECT statement from the
DB? I've been under the assumption (yeah, shaddup!) that db-driven client
vars were happy residents of No Locks Needed Here Land... where everybody
can live peacefully. Or, do db-driven client vars live in the slumlord hell
of You Better Lock It And Sleep With A Gun Under The Pillow Land ???

Alan McCollough
Web Programmer
Allaire Certified ColdFusion Developer
Alaska Native Medical Center

> -----Original Message-----
> From: Nat Papovich [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, October 11, 2000 7:55 AM
> To:   Fusebox
> Subject:      RE: Idea? (Don't read it Marc.) 
> 
> A single request (and thus any variable in the request scope) cannot be
> shared by multiple users, but a single user can make multiple simultaneous
> requests. That is why cflocking session and client variables is important.
> 
> Nat Papovich {redacted for brevity. Aint'cha glad?}
----------------------------------------------------------------------------
--
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to