> What are the real performance issues with having global
> client variables enabled?
If you're using a datasource to contain Client variables, then there's a
query every time they're read or written. That's significant compared to
using Session variables, especially if you're putting large strings in them,
such as WDDX packets, to get the same functionality as you could get by
storing queries or arrays in Session variables.
> I just did some testing and it seems HITCOUNT increases
> with each client variable change on a different page within
> an app. What's the point of Hitcount if it's updated everytime
> a client variable is changed? It doesn't tell you how often
> someone visits your site, but rather how often your client
> variables change. I mean has anyone found a use for this
> field? No wonder your registry explodes if you keep this
> stuff in the registry....
When you set up a datasource as a Client variable repository, there's a
setting which allows you to disable global client variable updates. When you
select this setting, HITCOUNT will behave as you've described above. If you
clear the setting, HITCOUNT should increment for every page requested by the
user associated with the Client variables, instead of it just updating when
a variable is changed.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
