> I'm sure this is a really really stupid question, but, what
> would happen if you wrapped the whole template in CFLOCK?
You'd increase the likelihood that the lock would interfere with another
lock. CFLOCK essentially does something analogous to locking in a database.
When you execute a complex database transaction, and that transaction locks
all the resources it touches, another person running that transaction will
have to wait longer in a queue before their transaction can run, and if it
takes too long, their time will run out. This creates a bottleneck. You can
have the same problems with CFLOCK, so just like with a database
transaction, you want your CFLOCK to be as short and quick as possible.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
