Storing Read-Only Data in ASP.NET Application Cache

See more:

application

.NET4

cache

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