Larry:
You could simply try and see if it works, but yes, you ought to be able to.
It'll behave much like you describe - having one dataset available for all
users. You might want to read up on datasets and multithreading, but if
you are doing read-only access on your dataset you should be ok.
On a side note, I much prefer the cache...yes it's true that it might be
dumped if the memory is low, but .Net is much better at handling memory than
you are. If you put the DataSet in the Application, you are pinning it in
memory - memory .Net might need to make things run. Unless generating your
dataset takes a very very long time, I'd reconsider using the Cache.
Karl
--
MY ASP.Net tutorials
http://www.openmymind.net/ - New and Improved (yes, the popup is annoying)
http://www.openmymind.net/faq.aspx - unofficial newsgroup FAQ (more to
come!)
"Lawrence Chang" <la************@rogers.com> wrote in message
news:cN********************@rogers.com...
Hi My friends,
Can I save dataset object to an application variable? I want all the
customer use this dataset. and diffrent customer create diffrent dataview
object from this dataset, so it don't need to connect to database
everytime . I know I can use cache object , but cache object can be
deleted automatically if server's memory is low, is this correct?
Would you like to give me more information about how to improve database
webform performace.
Thanks ahead.
Larry
Thanks
