2 questions:
we have an n-tier architecture (UI, BL, DAL, DB) and some common classes
that defy this structure like lookups. Those lookups actually handle their
own db access... but that's not important.
I have now implemented caching in our static lookup class via
"HttpContext.Current.Cache".
a. Is that correct?
b. when, why, and how would I use the System.Web.Caching.Cache?
Thanks,
Alex
Alvin Bruney [MVP] - 12 Mar 2004 17:42 GMT
It's as correct as you make it. Architecture questions don't have
straightforward answers. I suppose your cache would be another layer if you
chose to impliment it as another (security) tier after UI but before BL or
you could incorporate it into the UI layer. It depends.
I would use this as a security tier (ST- since we are bent on using
acronyms) where user authentication is done. This tier would sit behind the
UI tier. That is just one approach though for obvious reasons their may be
different approaches.

Signature
Regards,
Alvin Bruney [ASP.NET MVP]
Got tidbits? Get it here...
http://tinyurl.com/3he3b
> 2 questions:
>
[quoted text clipped - 10 lines]
>
> Alex