tracker issue : CF-3036929

Problem:

Please enable some way for end users to be able to know what client storage mechanism they're using. Yes, I realize it's set in application.cfm/cfc or takes its value from the Admin, but sometimes
one may guess wrong following those dots.

I've learned only today that there is in fact an undocumented way to get this info: #Client.getPersistSettings().get("clientstorage")#

BTW, that's not exposed in the Client scope if you dump it (cfdump var="#client#", which only shows what variables are set in the scope. One needs to know this method existed to ever find it.

Right now, other than this, there's no documented way to programatically determine what the current client scope is. 

Why might you need to? Sure, one could set it in either application.cfm or application.cfc (and the latter would override the former), but since such code could include or invoke other application.cfm/cfc files, it can just be very difficult to know what client storage one is using. Also, one might not set them, but then not have access to the CF Admin, so can't know which they're really using.

The info is here, in this function. We just need a way to expose it. It would be to also go ahead and expose for the given client storage identified what its settings are for number of days before a purge and whether disable global variable updates are en/disabled. These are the settings viewable otherwise only by one with access to the CF Admin (they're set for either registry or DSN-based client variable repositories.) There is no such value for the Cookie type, so they could be returned empty for that type.
Method:


Result:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3036929

External Customer Info:
External Company:  
External Customer Name: charlie arehart
External Customer Email: 03D0090C44723473992015D5
External Test Config: 12/02/2008

Attachments:

Comments: