Client Variables:

When set: Stored to Registry after briefly being held in RAM When got: Gotten from Registry and (briefly) stored to RAM before sent to user

Anything before going to the Hard Drive would have at least a brief stay in RAM

Session Variables:

When set: Put in RAM When got: Retrieved from RAM

You figure on this

Gregory Harris Web Developer ____________ The Stirling Bridge Group, LLC *We Engineer Internet Business Solutions* TEL: (949) 707-1534 FAX: (949) 707-1535

----- Original Message ----- From: "Andy Ewings" {andy.e@thoughtbubble.net> To: "CF-Talk" <cf-talk@houseoffusion.com> Sent: Monday, April 23, 2001 9:50 AM Subject: RE: Session VS Client

> >Client variables are probably a better choice if you think you're going to > >cluster your application on multiple servers, but on a single server, > >session variables will perform much better, assuming that there's enough > >emory to hold them. > > Yup agree....but I think you have answered my initial question - in that > session vars are more intensive when it comes to Server RAM > > ------------------------------------------------------------------ > Andrew Ewings > Project Manager > Thoughtbubble Ltd > http://www.thoughtbubble.net > ------------------------------------------------------------------ > United Kingdom > http://www.thoughtbubble.co.uk/ > Tel: +44 (0) 20 7387 8890 > ------------------------------------------------------------------ > New Zealand > http://www.thoughtbubble.co.nz/ > Tel: +64 (0) 9 488 9131 > ------------------------------------------------------------------ > The information in this email and in any attachments is confidential and > intended solely for the attention and use of the named addressee(s). Any > views or opinions presented are solely those of the author and do not > necessarily represent those of Thoughtbubble. This information may be > subject to legal, professional or other privilege and further distribution > of it is strictly prohibited without our authority. If you are not the > intended recipient, you are not authorised to disclose, copy, distribute, or > retain this message. Please notify us on +44 (0)207 387 8890. > > > > -----Original Message----- > From: Dave Watts [mailto:dwatts@figleaf.com] > Sent: 23 April 2001 17:31 > To: CF-Talk > Subject: RE: Session VS Client > > > > the general opinion is that client vars are more efficient > > than session variable, as long as the administrator is configured > > to store client variables in a database, otherwise it stores client > > variables in the registry which is less efficient that using session > > vars. > > Either you've got the general opinion wrong, or the general opinion is > itself wrong (or at least oversimplified). > > All other things being equal, it's more efficient to store something that > will be reused in memory than it is to retrieve it from a database each time > it's needed. When you use session variables, you're storing something in the > local memory of the CF server. When you use client variables, CF has to > continually go get them whenever they're needed, if they're stored in a > database or in the registry. > > Client variables are probably a better choice if you think you're going to > cluster your application on multiple servers, but on a single server, > session variables will perform much better, assuming that there's enough > memory to hold them. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > voice: (202) 797-5496 > fax: (202) 797-5444 >