first access to the app by a browser. One technique that you may be
interested in is with clustered servers.... What we did was before we
brought the server onto the cluster upon bootup, we would run a batch
file which would run the home page of the site which would load all
these application variables into memory, and then when it was finished
loading into memory we would add the server to the cluster. This meant
the first time a user actually hit the site was very fast.
Does that make sense? I'll send out the code for the batch file if I
can find it.
Steve
paul smith wrote:
>
> Very cool. Thanks!
>
> best, paul
>
> PS> A small point. Would this app run queries upon bootup, or upon first
> access of the app by a browser?
>
> At 10:34 AM 8/26/00 -0400, you wrote:
> >I've just hit upon a technique that would mean we only ever need to use
> >cflock two times in a fusebox home application. This is for application
> >variables, session and server variables would need to do the same too i
> >imagine (personally i never use them)
> >
> >First I want to propose a new filename, qry_globals.cfm the point of the
> >file is to store application wide queries, it would sit in the root
> >directory of your home application. It would run queries from the
> >database upon booting up the server then store the variables into
> >memory.
>
> ------------------------------------------------------------------------------
> To Unsubscribe visit
>http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
>message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
