Re: CFLOCK and Session variables

2001-09-10 Thread Matt Robertson
PROTECTED] To: CF-Talk [EMAIL PROTECTED] Sent: Wednesday, September 05, 2001 9:45 AM 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

Re: CFLOCK and Session variables

2001-09-10 Thread Chris Norloff
Have you tried this doc? http://www.allaire.com/handlers/index.cfm?ID=17318Method=Full best, Chris Norloff -- Original Message -- from: Gonzo Rock [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] date: Wed, 05 Sep 2001 09:45:21 -0700 A couple of questions

CFLOCK and Session variables

2001-09-10 Thread Yager, Brian T Contractor/NCCIM
I know we have discussed this a good bit lately but I am still needing some understanding. In my application, I make MANY session variables. I use these variables to check certain things on many pages. Because of the past threads on this I have surrounded them with CFLOCK tags. NowCan

RE: CFLOCK and Session variables

2001-09-10 Thread Tyson Vanek
Contractor/NCCIM [mailto:[EMAIL PROTECTED]] Sent: Monday, September 10, 2001 2:27 PM To: CF-Talk Subject: CFLOCK and Session variables I know we have discussed this a good bit lately but I am still needing some understanding. In my application, I make MANY session variables. I use these variables

RE: CFLOCK and Session variables

2001-09-07 Thread Kwang Suh
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

RE: CFLOCK and Session variables

2001-09-07 Thread Daniel Lancelot
:[EMAIL PROTECTED]] Sent: 05 September 2001 17: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

Re: CFLOCK and Session variables

2001-09-07 Thread BEN MORRIS
A user with 2 browser windows open both on your site, or if your site has frames would be 2 situations where there could be a session var conflict. - Ben Gonzo Rock [EMAIL PROTECTED] 09/05/01 12:45PM A couple of questions that I can't seem to sort out from reading the DOCS... 1. Why

Re: CFLOCK and Session variables

2001-09-07 Thread Don Vawter
10:45 AM Subject: CFLOCK and Session variables My impression is that: Session.var is NOT shared, Client.var is NOT shared, Application.var IS shared 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

RE: CFLOCK and Session variables

2001-09-07 Thread Pete Freitag
[mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 05, 2001 12:45 PM 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

RE: CFLOCK and Session variables

2001-09-06 Thread Tilbrook, Peter
- 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

CFLOCK and Session variables

2001-09-05 Thread Gonzo Rock
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

Problems with CFLOCK and session variables?

2001-05-08 Thread Gregory Harris
Ok, what is the consequence for failing to lock a session variable? Right now it appears that with some unlocked session variables that we have on an application that we inherited, it appears to be generating some huge memory leaks in ColdFusion whenever we're going through the application.

RE: Problems with CFLOCK and session variables?

2001-05-08 Thread Cameron Childress
-Talk Subject: Problems with CFLOCK and session variables? Ok, what is the consequence for failing to lock a session variable? Right now it appears that with some unlocked session variables that we have on an application that we inherited, it appears to be generating some huge memory leaks

Re: Problems with CFLOCK and session variables?

2001-05-08 Thread Jamie Jackson
Exclusively lock all of your sets, and ReadOnly lock all of your reads (references). Just do it, it's not too tough. :) Watch out for application variables too. Jamie On Tue, 08 May 2001 11:15:20 -0700, Gregory Harris [EMAIL PROTECTED] wrote: Ok, what is the consequence for failing to lock

Re: CFLOCK on Session Variables

2000-09-01 Thread Jim McAtee
-Original Message- From: Kevin Miller [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED]; [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Thursday, August 31, 2000 6:57 PM Subject: RE: CFLOCK on Session Variables I love Cold Fusion, but this is a really rotten basket that screams

RE: CFLOCK on Session Variables

2000-08-31 Thread Zachary Bedell
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Okay... Last time now... This is your server [holds up egg]. This is your server with out locking [*sizzle*]. Any questions? But seriously... Please allow me to clear up a couple of misconceptions in this post. Does a CFLOCK with

RE: CFLOCK on Session Variables

2000-08-31 Thread Kevin Miller
I love Cold Fusion, but this is a really rotten basket that screams of design flaw. Do we have a commitment from Allaire that this mess is going to get fixed in the next version? Locking needs to be handled on the back-end and not be dependant upon programmers to behave themselves, especially

Re: CFLOCK on Session Variables

2000-08-31 Thread Jim McAtee
-Original Message- From: Zachary Bedell [EMAIL PROTECTED] To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] Date: Thursday, August 31, 2000 11:28 AM Subject: RE: CFLOCK on Session Variables Okay... Last time now... This is your server [holds up egg]. This is your server with out locking

RE: CFLOCK on Session Variables

2000-08-31 Thread Dave Watts
I love Cold Fusion, but this is a really rotten basket that screams of design flaw. Do we have a commitment from Allaire that this mess is going to get fixed in the next version? I don't think Allaire has committed to any specific changes in locking. Locking needs to be handled on the

RE: CFLOCK on Session Variables

2000-08-31 Thread Zachary Bedell
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Okay... Last time now... This is your server [holds up egg]. This is your server with out locking [*sizzle*]. Any questions? *snip* Thanks for the extensive explanation. A couple finer points still aren't quite clear to me. When

RE: CFLOCK on Session Variables

2000-08-31 Thread Dave Watts
Thanks for the extensive explanation. A couple finer points still aren't quite clear to me. When you say "will lock all of your session vars", from the rest of your explanation, I gather you don't mean all of the session variables from all sessions in all applications running on the

RE: CFLOCK on Session Variables

2000-08-31 Thread Kevin Miller
Point well taken. There will be certain scenarios, as you have outlined, where manual locking will always be important. Something as fundamental and universal as variable locking should not be one of them. Kevin Dave Watts [EMAIL PROTECTED] 08/31/00 01:11PM I love Cold Fusion, but this is

CFLOCK on Session Variables

2000-08-30 Thread Jim McAtee
A couple of general questions regarding locking session variables (CF 4.0.1): Does a CFLOCK with name="#session.sesionid#" only lock the variables in memory for that particular session, or does it lock all session variables for the application? The CF 4.0.1 documentation for CFLOCK has the

RE: CFLOCK on Session Variables

2000-08-30 Thread Ed Toon
It locks all of the CFLOCK blocks where name="#session.sessionid#". Practically speaking, it locks all of the session variables for that particular session. Ed -- Archives: