> the situation which causes the most overhead on the server
> and stores duplicate data.
> Session variables can get you faster into trouble then
> application variables because the CMFX garbage collector is
> only called once a time and not on each request. So it is
> very important to minimize this types of situations :-)
As long as you have sufficient memory on the server, and you don't keep
session data around too long, this usually isn't a problem. If you really
have that many people using the same queries, it's probably worth building
some sort of shared cache, either in the Application scope or using
CACHEDWITHIN/CACHEDAFTER, but in my experience most people using
query-by-example interfaces aren't performing the same searches anyway.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
