What are the real performance issues with having global client variables
enabled?

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....

Below is the code I used to test this.

<---Application.cfm--->
<CFAPPLICATION name="northwind" clientmanagement="yes"
clientstorage="northwind">

<---app_locals.cfm--->
<cfparam name="client.color" default="">
<cfparam name="client.text" default="">
<cfparam name="fuse" default="">

<---index.cfm--->
<cfinclude template="app_locals.cfm">
<cfswitch expression="#fuse#">
 <cfcase value="1">
  <cfinclude template="test_clientvar.cfm">
 </cfcase>
 <cfcase value="2">
  <cfinclude template="test_clientvar_2.cfm">
 </cfcase>
 <cfdefaultcase>
  <cfinclude template="test_clientvar.cfm">
 </cfdefaultcase>
</cfswitch>

-----changes client.text to green and client.color to blue
<---test_clientvar.cfm--->
page 1<br><br>
<cfset client.color = "blue">
<cfoutput>
#client.color#<br>
#client.hitcount#<br>
</cfoutput>
<cfset client.text = "green">
<cfoutput>
<b>
#client.text#<br>
#client.hitcount#<br>
</b>
</cfoutput>
<a href="index.cfm?fuse=2">next</a>

-----changes client.text to blue and client.color to green
<---test_clientvar_2.cfm--->
page 2<br><br>
<cfset client.text = "blue">
<cfoutput>
#client.text#<br>
#client.hitcount#<br>
</cfoutput>
<cfset client.color = "green">
<cfoutput>
<b>
#client.color#<br>
#client.hitcount#<br>
</b>
</cfoutput>
<a href="index.cfm?fuse=1">next</a>

------------------------------------------------------------------------------
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.

Reply via email to