[thelist] CF: Determining which DB used.

[Raymond Camden]

> ><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> > From: Raymond Camden
> >
> > Security reasons. That's the official reason. 
> ><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> 
> bah.  i can query the information directly by hand typing in 
> these variables with dots in them.  unless there is 
> additional, undocumented variables that would be exposed by 
> the server scope being a structure, i see no security risk.  
> power to the developer, right?

I should have been more precise. The 'default' Server values are not
hidden per se. They are in the docs. I was replying more to "Why can't I
use Server like a Struct". The answer is, that if you could, it could be
a potential security risk, not because of the data in the default server
vars, but because of other data, for example, maybe you are at an ISP.

Now, that being said, I agree w/ you 100% that it's not a valid
reason...  however, it's not a big deal if you just use a substruct
under Server.

> ><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> > Personally, I don't agree that it's a good idea, but,
> > what do you do. 
> ><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> 
> send an email to wish-coldfusion at macromedia.com i guess.

Well, I'm pushing for it myself internally, but of course, I'm too low
on the totem pole to make such decisions. ;)


> ><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> > If you want to use the Server scope for your app, I
> > suggest doing Server.App instead of just Server, that
> > way you can examine the structure w/ StructKeyList, etc. 
> ><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> 
> i see no indication that server.app exists.  are you 
> suggesting reconstructing the dotted variables into your own 
> structure (which also has a dot in the variable name, tsk 
> tsk)?  if being able to walk the collection is important to 
> the functioning of an app, then i agree that recreating the 
> information as a true structure of structures would be the best route.

No, what I meant was:

<CFSET Server.MyApp = StructNew()>

Then put your crap in there.

-Ray