hi,

Can I pose a quick question (I did a a search for -application variables- but didnt find anything relevant to my needs but appologise if this has been asked manytimes over....

I was taught to code in asp without (or very infrequeltly) using application and session variables. I understand they impact performance/memory usage and if objects are created, cause big issues if it not threaded appropriately...

my question is this, I wrote an NT service and ask it to be installed on a webserver. At that point our tech area said that my work was overkill and I should re-write my app as script/dll and using application variable.. Management agreed and I change my design.


I have now quite alot on info as application vars including a couple of objects (ado resordsets) and am concerned that I will encounter problems..

If I used session vars then I would have one ser of data per user therefore would run out of memory on the server if there were alot of users...

Am I right is saying that I only have one set of data when using app vars? Therefore there is no problem and I am being to cautious (IIS doesnt do anything stupid like copy them per usage....)

Im not quite sure.... any better perspective would be appreciate.

Cheers, A.J.P. Ext 4290.