RE: Preferred clientstorage setting for client variables
> What is the "best" way to store client variables? We are in > the process of completely redesigning our website and > considering changing the "clientstorage" attribute in > cfapplication from a named SQL datasource to "Cookie" to > prevent having 100,000's of records pile up on our SQL server. > > The primary use of this would really just be to allow the > user to have their login status "remembered" so they would > not have to log into our site every time. > > Any arguments one way or the other? I would generally recommend the use of database storage, if you have a reliable database. SQL Server is certainly reliable enough for this. Just make sure you purge records as appropriate, and disable global client variable updates if they're not needed. There are several problems with using cookies to store any significant data: you don't have any control over them, they can become large and unwieldy over time, they may get lost or truncated for unexpected reasons. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! This email has been processed by SmoothZap - www.smoothwall.net ~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJP Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:276267 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
RE: Preferred clientstorage setting for client variables
> Writing to the db. As robust as your db is. Nobody loves a > thing that executes a db read and write at every page > request, but at least there are no vultures circling your > server when you do it this way. The problems you will cause > will be manageable, one way or the other. Unless you need to track the system-generated Client variables (hitcount, lastvisit), you can avoid an update for each page that doesn't otherwise change Client variables by disabling the appropriate option in the CF Administrator. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! This email has been processed by SmoothZap - www.smoothwall.net ~| Macromedia ColdFusion MX7 Upgrade to MX7 & experience time-saving features, more productivity. http://www.adobe.com/products/coldfusion?sdid=RVJW Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:276266 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Re: Preferred clientstorage setting for client variables
dont forget that these days people have their browsers configured to remember stuff for them, so they may not need a cookie to do that - Original Message From: james carberry <[EMAIL PROTECTED]> To: CF-Talk Sent: Wednesday, April 25, 2007 2:58:06 PM Subject: Preferred clientstorage setting for client variables What is the "best" way to store client variables? We are in the process of completely redesigning our website and considering changing the "clientstorage" attribute in cfapplication from a named SQL datasource to "Cookie" to prevent having 100,000's of records pile up on our SQL server. The primary use of this would really just be to allow the user to have their login status "remembered" so they would not have to log into our site every time. Any arguments one way or the other? Thx! -James Carberry ColdFusion MX Certified Developer and Instructor ~| Upgrade to Adobe ColdFusion MX7 The most significant release in over 10 years. Upgrade & see new features. http://www.adobe.com/products/coldfusion?sdid=RVJR Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:276265 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Re: Preferred clientstorage setting for client variables
On 4/25/07, james carberry wrote: > What is the "best" way to store client variables? Better way to phrase that is "what is the least bad way?" :-) Cookies are a disaster. To make a long story short you can't count on them being present all the time, and you have to wait for a trip to the client and back before you can use one thats been set (unless that behavior has changed over the years). Plus they can be hacked ore easily, being client-side. All of the true nightmares I have experienced with cvars have been when I discovered the site owner was storing them in cookies. Writing to the registry... It works, but horrific consequences possible if a write goes bad. Other nasties possible. For example your site gets hit by an ill-behaved bot two zillion times and it creates two zillion entries... in your registry. Your now-uber-bloated registry. 'nuff said. Writing to the db. As robust as your db is. Nobody loves a thing that executes a db read and write at every page request, but at least there are no vultures circling your server when you do it this way. The problems you will cause will be manageable, one way or the other. Lest you think I hate cvars, I do not. I still use them at least to some degree, although mostly in legacy apps. I try to rely on session vars. -- [EMAIL PROTECTED] Janitor, The Robertson Team mysecretbase.com ~| Upgrade to Adobe ColdFusion MX7 The most significant release in over 10 years. Upgrade & see new features. http://www.adobe.com/products/coldfusion?sdid=RVJR Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:276264 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Re: Preferred clientstorage setting for client variables
Database here. Stay away from storing in cookies as much as possible. On 4/26/07, james carberry <[EMAIL PROTECTED]> wrote: > > What is the "best" way to store client variables? We are in the process of > completely redesigning our website and considering changing the > "clientstorage" attribute in cfapplication from a named SQL datasource to > "Cookie" to prevent having 100,000's of records pile up on our SQL server. > > The primary use of this would really just be to allow the user to have > their login status "remembered" so they would not have to log into our site > every time. > > Any arguments one way or the other? > > Thx! > > -James Carberry > ColdFusion MX Certified Developer and Instructor > > ~| Macromedia ColdFusion MX7 Upgrade to MX7 & experience time-saving features, more productivity. http://www.adobe.com/products/coldfusion?sdid=RVJW Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:276263 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4