Ryan, you're right on, mainly. The typical progression in developers, and/or in large projects, is, start with client variables in the registry. Learn quickly not to do that, switch to cookies until they can be stored in a database. With traffic, you will eventually learn that your database / db server can't handle the load, or the communication between CF and your DB is becoming too great. Switch back to cookies until you can find a permenant client var work-around.
Hopefully by this time client variable calls aren't too integrated into your site, or making the switch will be a huge problem. Meanwhile, if you store wddx in client variables, you will quickly learn about the maximum size of a cookie, and the adverse effects it has on different versions of popular browsers when that limit is reached. To make a long story short, don't do it: http://www.dopefly.com/techblog/entry.cfm?entry=77 Of course, not everyone will have these problems. If you have a small site with little traffic, even storing your client variables in the registry may not hurt anything, and can be fine for years and years. But when you build a popular site or get a few million hits a month, you're in for a ride. -nathan strutz http://www.dopefly.com/ On 11/28/05, Ryan Guill <[EMAIL PROTECTED]> wrote: > I have never really found a need for client variables. What benefit > do they really offer? The only time I could see using them is when > you had something that you might think about storing in a cookie. I > rarely come across a need like that where I dont really want a cookie, > and if I do I usually just store it in the session. Am I missing > something there? > > On 11/28/05, Russ <[EMAIL PROTECTED]> wrote: > > Are you still running another server on BD? How is BD handling this issue? > > > > -----Original Message----- > > From: Michael Dinowitz [mailto:[EMAIL PROTECTED] > > Sent: Monday, November 28, 2005 1:38 PM > > To: CF-Talk > > Subject: pseudo-memory leak > > > > I've written up my thoughts on what looks like the problem that the House of > > Fusion server was facing for the last few weeks. It's a problem that > > probably affects others but I'm not going to comment on how wide spread it > > is until the full write-up on Fusion Authority. These are just my notes and > > thoughts. > > http://www.blogoffusion.com/index.cfm/2005/11/28/pseudomemory-leak > > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225453 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
