We're running an application that can have many customers (100+).

This application is a single ASP.NET installment. We use seperate folders
to hold XML settings for each customer.

Each Customer has a different DB to pull it's data from. And each Customer
has many users.

We're thinking of implementing caching on some of the most frequently viewed
pages. I've only learned a bit about caching, and have some questions about
it.

If Customer X logs onto our system and views page A, page A will be cached.
Now if Customer Y logs in, will he see X's page A or his own page?

Each customer has their own URL to go to, which fowards them to their
settings directory, which then forwards them to the application itself,
running on their settings.

I just have to make sure that Customers only see their own pages, and no one
elses.

Ryan,

it is difficult to answer your question without a lot more information about
your code, setup, environment and so on.

I advise you to check out:
http://msdn.microsoft.com/library/en...utputcache.asp
which gives you an overview + links to details about ASP.NET Caching.


--

Best regards,
Geir Aamodt
geir.aamodt(AT)bekk.no

"Ryan Ternier" <rternier (AT) icompasstech (DOT) com> wrote