> > Session variables are more robust, certainly (when stored in a
> > database), but they're definitely quite a bit slower.
>
> I didn't know session vars were stored in a DB, I thought they were
> only stored in memory.
You're right, of course. I'm a bit woozy today. Sorry about that. I meant
that Client variables are more robust (which is, of course, why you're using
them!).
> Ok, I'm not debating whether *anything* should be stored in memory.
> My query caching works nicely. My *specific* problem was CF restarting
> itself and dropping session vars I was using to keep people "logged
> into" my application. I was using them to "maintain state". I found
> that session vars were therefore unreliable so I switched to client
> vars.
And, of course, for your app you're doing the right thing.
That's one of the problems with email lists. Very often, a discussion
revolves around "which is better", when it's often the case, as it is now,
that neither is better. It completely depends on the needs and circumstances
of your application. If you're having stability problems with memory
variables, as you and many others are, you'd be a fool to use them because
they're more efficient - who cares how efficient your app is if it's always
crashing?
I'd be the first to say that each has an appropriate place for use.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
