> 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
