Simple locking question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I read the Allaire article on locking and am now using locks when working with session variables. Now I am wondering if I should be using session variables at all? In my app, the user logs in and at that time I put a bunch of information about them (email, username, customerid, firstname, lastname, etc) into session variables (using Application.cfm), which I then access all over the place to prefill form fields, do db inserts, etc. Of course, I have to put locks around every use of the session variables, often multiple locks on the same page. Is this the right way to approach this? Should I use some other scope or method? c - -- Chris Lott <[EMAIL PROTECTED]>| IT Manager|p907-474-3494 -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 for message encryption and authentication: USE PGP! Comment: KeyID: 0x51046CFD iQA/AwUBOb7VKNaLYehRBGz9EQITPACg0yaD/xZptcxSkDX/8uttVyekXoUAnjIs j78w7mSYWWtKNFsbopRwDD3m =N3xp -END PGP SIGNATURE- -- 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.
Re: Simple locking question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I read the Allaire article on locking and am now using locks when working with session variables. Now I am wondering if I should be using session variables at all? In my app, the user logs in and at that time I put a bunch of information about them (email, username, customerid, firstname, lastname, etc) into session variables (using Application.cfm), which I then access all over the place to prefill form fields, do db inserts, etc. Of course, I have to put locks around every use of the session variables, often multiple locks on the same page. Is this the right way to approach this? Should I use some other scope or method? c - -- Chris Lott <[EMAIL PROTECTED]>| IT Manager|p907-474-3494 -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 for message encryption and authentication: USE PGP! Comment: KeyID: 0x51046CFD iQA/AwUBOb7VKNaLYehRBGz9EQITPACg0yaD/xZptcxSkDX/8uttVyekXoUAnjIs j78w7mSYWWtKNFsbopRwDD3m =N3xp -END PGP SIGNATURE- -- 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.
RE: Simple locking question
Personally I use Client variables located in a database exclusively. That way my application can easily made to be cluster aware and the database takes care of the locking. Robert Everland III Web Developer Dixon Ticonderoga -Original Message- From: Chris Lott [mailto:[EMAIL PROTECTED]] Sent: Friday, September 15, 2000 2:32 PM To: [EMAIL PROTECTED] Subject: Re: Simple locking question -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I read the Allaire article on locking and am now using locks when working with session variables. Now I am wondering if I should be using session variables at all? In my app, the user logs in and at that time I put a bunch of information about them (email, username, customerid, firstname, lastname, etc) into session variables (using Application.cfm), which I then access all over the place to prefill form fields, do db inserts, etc. Of course, I have to put locks around every use of the session variables, often multiple locks on the same page. Is this the right way to approach this? Should I use some other scope or method? c - -- Chris Lott <[EMAIL PROTECTED]>| IT Manager|p907-474-3494 -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 for message encryption and authentication: USE PGP! Comment: KeyID: 0x51046CFD iQA/AwUBOb7VKNaLYehRBGz9EQITPACg0yaD/xZptcxSkDX/8uttVyekXoUAnjIs j78w7mSYWWtKNFsbopRwDD3m =N3xp -END PGP SIGNATURE- -- 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. -- 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.
Re: Simple locking question
> Personally I use Client variables located in a database exclusively. That > way my application can easily made to be cluster aware and the database > takes care of the locking. So at an abstract level, how does that work? Currently I just assign the needed information to session variables and access them at all times. If I store them in a database do I have to keep track of the user across all the pages manually? c -- Chris Lott <[EMAIL PROTECTED]>| IT Manager|p907-474-3494 -- 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.
RE: Simple locking question
It works the same as session variables, though not quite as fast they work a lot better and I don't have to worry about the locking all over the place. They use the same session.urltoken as session variables. Bob Everland -Original Message- From: Chris Lott [mailto:[EMAIL PROTECTED]] Sent: Friday, September 15, 2000 8:20 PM To: [EMAIL PROTECTED] Subject: Re: Simple locking question > Personally I use Client variables located in a database exclusively. That > way my application can easily made to be cluster aware and the database > takes care of the locking. So at an abstract level, how does that work? Currently I just assign the needed information to session variables and access them at all times. If I store them in a database do I have to keep track of the user across all the pages manually? c -- Chris Lott <[EMAIL PROTECTED]>| IT Manager|p907-474-3494 -- 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. -- 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.
RE: Simple locking question
> It works the same as session variables, though not quite as fast > they work a > lot better and I don't have to worry about the locking all over the place. > They use the same session.urltoken as session variables. They do work pretty much the same, but you would need to keep in mind that you can't store a complex datatype (IE: Query or Structure) in a Client variable without serializing it first (WDDX). Also, client variables typically persist much much longer than Session vars, depending on how you have them configured. -Cameron Cameron Childress ElliptIQ Inc. p.770.460.7277.232 f.770.460.0963 -- 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.
