Application variables

  Request variables and Application variables are two completely different things, so i don't know if they deserve direct comparison.  It depends what you want to use them for.   Request variables exist during a single page execution.   They are not persistent across page requests.   You do not need to lock them.   If 100 users hit the same page at once, then 100 instances of each request variable will exist simultaneously.   Request variables are available to all templates in the request, including custom tags.  Because of this, I like to say that they are global to the request.  Many people use them to avoid passing parameters into custom tags.  I feel that is the only use for them over local variables (I.E. the variables scope ).   Application variables are locked into an application via the cfapplication tag.   They are persistent across page requests.   You really should lock them.    If 100 users hit the same page at once, then only 1 copy of each application variable will exist.    They are available to all templates in the request, including custom tags.    Does that give you enough to go on? At 10:40 AM 11/25/2002 -0800, you wrote: >From: "Andy Ousterhout" <andy@omygoodness.com> >To: "CF-Talk" <cf-talk@houseoffusion.com> >Sent: Monday, November 25, 2002 10:31 AM >Subject: RE: Application variables > > > > What's are the Pro's and Con's  of using Request Variables over >Application > > Var? > > -- Jeffry Houser | mailto:jeff@farcryfly.com DotComIt, Putting you on the web AIM: Reboog711  | Phone: 1-203-379-0773 -- My CFMX Book: <http://www.amazon.com/exec/obidos/ASIN/0072225564/instantcoldfu-20>; My Books: http://www.instantcoldfusion.com My Band: http://www.farcryfly.com