It's the application name, not the session name. We do something like this on our dev server, so each developer can have independent instances of the application without stepping on each others application and session scopes, etc. and without having to remember to manually rename the application for each instance.
On 3/19/07, Peterson, Chris <[EMAIL PROTECTED]> wrote: > > I inherited a web site that is having session management issues, and > using a good amount of ram. > > In the application.cfm file, there is the following session code: > > <cfapplication sessionmanagement="yes" > name="#Hash(GetCurrentTemplatePath())#" setclientcookies="no"> > > Now, can anyone tell me why you would want, on a web site that requires > users to login, to set the session name based on the template? > > Chris > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 by Adobe® Dyncamically transform webcontent into Adobe PDF with new ColdFusion MX7. Free Trial. http://www.adobe.com/products/coldfusion?sdid=RVJV Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:272978 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
