RE: Caching Design
- From: "Santhi Maadhaven" <SanthiMaadhaven@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 2 Aug 2005 00:29:02 -0700
No u dont need to move the caching stuff to one place.There will be something
which needs to be cached at the UI level and something which needs to be
cached at the business level.Take for example,if you have some static html or
static content that will be displayed throughout u can cache this at the UI
level.At business level,u can cache the things which is frequently accessed
from database.business level is the best place for it.
"Jim Douglas" wrote:
> My setup is web application, middle tier for business logic and data access.
> I have static data cached on the GUI and in the middle tier. The stuff
> cached in the web application is to populate dropdownlists, etc. The data
> cached in the middle tier is larger, company locations, etc.
>
> Should I cache everything in the middle tier so that it's in one place? I
> realize that the front end would then have to go across the wire to get the
> cached data but is it worth it? What are you guys/gals doing?
>
>
> Thanks!
>
> Jim Douglas
>
>
>
.
- References:
- Caching Design
- From: Jim Douglas
- Caching Design
- Prev by Date: Re: Accessing Second Item causes problem
- Next by Date: RE: win2k3 sp1 causes System.Net.WebClient.OpenRead to throw WebEx
- Previous by thread: Caching Design
- Next by thread: RE: win2k3 sp1 causes System.Net.WebClient.OpenRead to throw WebEx
- Index(es):
Relevant Pages
|
