Why is Cache Property used in BizObject ?

Scott663 · March 8th, 2007, 12:51 PM

What is the purpose of the Cache property in the BizObject? Why not just reference the 'Cache' object directly in the BLL modules? I assume this is just another design consideration that provides a single point to alter/enhance the caching scheme if desired, but I'm not sure...

Also, why couldn't a simple variable declaration be used instead of a property? The following variable declaration seems more concise than the property declaration used in the code.

Code:

Protected Shared ReadOnly Cache As Cache = HttpContext.Current.Cache

Property declaration used in BizObject.vb code:

Code:

Protected Shared ReadOnly Property Cache() As Cache
   Get
      Return HttpContext.Current.Cache
   End Get
End Property

Is this a semantical preference or is there a difference in functionality I'm missing?

englere · March 8th, 2007, 10:34 PM

Properties are used to allow hiding the implementation. This lets us change the getter later without breaking any of the other code.

In this particular case, you have to weigh the odds that you might want to replace the cache in the future. I probably wouldn't have wrapped this particular item, but I'm not sure if Marco had other ideas on what he might want to do with it.

Eric

Scott663 · March 8th, 2007, 10:47 PM

That's what I thought but just wanted confirmation.

Your support throughout the forum is excellent!

Thanks Eric!