what you have to remember is that cookies are sent back and forth regardless unless the client has them disabled in his browser. Official *max*imum *size* for a HTTP *cookie* header is 4K. So the actual * cookie* will be slightly smaller. Some browsers will work with bigger * cookie*s, others won't. So it is never going to add much bandwidth.
On Wed, Sep 22, 2010 at 11:52 PM, Dan Baughman <[email protected]>wrote: > > My hesitation on cookie is adding the un-necessary bandwidth to every > request. > > I think the best move is a hybrid. > > 1) disable client vars using clientmanagement=no in your cfapplication > 2) set it to database or cookies. > > On Wed, Sep 22, 2010 at 2:57 PM, Russ Michaels <[email protected]> > wrote: > > > > > set the default to cookie like i said and u will have no issues. Note > what > > i > > said about the registry key if you wish to disable registry storage > > permanently. > > > > On Wed, Sep 22, 2010 at 6:44 PM, Dave Watts <[email protected]> wrote: > > > > > > > > > Why in the world would Adobe not use something like SQLite or Derby > for > > > > this, by default? > > > > > > Client variables predate the existence of SQLite or Derby. Client > > > variables were first introduced back in CF 2, if I recall correctly. > > > > > > Dave Watts, CTO, Fig Leaf Software > > > http://www.figleaf.com/ > > > http://training.figleaf.com/ > > > > > > Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on > > > GSA Schedule, and provides the highest caliber vendor-authorized > > > instruction at our training centers, online, or onsite. > > > > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:337347 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
