Depends on a number of things, like are you trying to save memory or get
more speed out of it, or just have all the data binded to a key for easy
access? Also depends on what you are building too. Personally I go for a lot
of independent structures so some kind of error won't corrupt the entire bag
(simplest= always works best/modular/fast to develop and debug). But if you
are building a massively related data structure then just put it all in one
structure.
----- Original Message -----
From: Scott Weikert <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 25, 2000 10:03 AM
Subject: Opinions on tuning...
> Ok gang, speak out -
>
> Two options, which does the peanut gallery think is superior?
>
> 1) Creating a structure within an application variable - structure having
> many many keys, with arrays full of options tied to each key -
>
> or
>
> 2) Creating multiple application variables, with a structure inside,
holding
> the same sort of array as above.
>
> Basically, option 1 is lumping all goodies in one big application
variable,
> option 2 is making one application variable for each set of goodies.
>
> Thoughts?
>
> --Scott
> --------------------------------------------------------------------------
----
> 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.
>
------------------------------------------------------------------------------
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.
