Storing Read-Only Data in ASP.NET Application Cache

Question

0.00/5 (No votes)

See more:

Hi,

I don't wish to seem that I am asking members on here to do my design work for me but I have a design-related question that I can't think how to evaluate without writing a load of code and doing some pretty detailed testing. I therefore wondered if I could run the basic idea past developers on here who have had a lot more experience than me and may simply be able to give me a quick yes/no whether I am on the right track or barking up the wrong tree.

I have a small quantity (<100 records) of data that is completely read-only. Users of the site can however form their own views of the data using search filters. I was therefore thinking of storing the actual DataSet in the Application cache and having each user build a DataView as needed.

Since the data is read-only and there are so few records, I was intending to do this with no locking when the DataViews are being built from the DataSet. Am I right in thinking that this should be fine?

(Note: I envisage the site will have no more than a handful of simultaneous users initially, but I obviously don't want the whole thing to fall over if I got, say, 100.)

Any other comments on the basic design would be very much appreciated.

Kind wishes, Patrick

Posted 6-Oct-11 9:09am

Patrick Skelton

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Not Active · Accepted Answer · 2011-10-06T09:59:00

Solution 1

A DataSet is a pretty "heavy" object and is not usually cached. Unless you have multiple DataTables within the DataSet there is no reason to use it. Creating an entity object or POCO may be a more efficient.

Posted 6-Oct-11 9:59am

Not Active

Comments

Patrick Skelton 7-Oct-11 4:15am

That is a good point. There is actually only one table to be stored. I didn't actually check if it was possible to build a DataView from just a table.

One of the dangers of using just one reference book as your main source of information; you just tend to do things the way they do them in the book.

Thank you.

- Patrick