I have a couple questions with the process.

1. Why did the author hard code the keys for caching data such as
"Articles_Category_" over saving it as a variable? Is there a reason for this?

2. Protected static void CacheData(string key, object data)
Could this method just be placed in BizObject once? Was there a hidden reason I don't see in placing it in all of BizObject subclasses?

I love this book, it was so easy to understand. Is the ASP.net 3.5 version of the book coming out soon?
I am contemplating writing the DAL over and use LINQ instead. Everything will be left the same except new Database objects will be link with LINQ. Does anyone see a problem with this approach?

What advantage would be gained by using a variable? Why would you ever want to change the cache key?


That's actually a good question. I don't see a reason it couldn't have been.


It's been done.

http://www.wrox.com/WileyCDA/WroxTit...47041569X.html

Shouldn't be a problem then.

__________________
Visit my blog at http://leedumond.com
Follow me on Twitter: http://twitter.com/LeeDumond

lee/crazy,

the reason for it being implemented in each base class is due to the configuration per provider i.e if you look, you'll see something along the lines of:

Cache.Insert(key, data, null, DateTime.Now.AddSeconds(BaseAccomodation.Settings. CacheDuration), TimeSpan.Zero);

so, you'd have no control over the CacheDuration per provider. a small point but may actually be desirable to have a long cache duration for some items and a short snappy one for other items (i actually cache the output of my usercontrols manually in a similar fashion but only cache them for anywhere between 60 and 120 secs - this believe it or not can have a profound impact on performance and is well worth looking implementing. this incidently is the main reason that i never use the objectdatasource to bind controls in the aspx page and instead just place a <div id="divRSS" runat="server" class="rightbox_wrapper lastbox" /> in the aspx page and in the page_load run a method that either get's the generated divs from the cache OR runs the BLL method to retireve the data and populate the markup from there. just one of my little foibles )

hope this helps..

__________________
jimi

http://www.originaltalent.com

Good point Jimi. I should have actually looked at the BeerHouse code, would have seen that the separate implementations allow for different durations.

BTW, you do know you can cache with the ObjectDataSource, right?

__________________
Visit my blog at http://leedumond.com
Follow me on Twitter: http://twitter.com/LeeDumond

lee - actually, i wasn't aware of that. however, i did actually drop using the ODS quite a while back due to requireing a more flexible and controlled approach to using my BLL data (plus, i'm not a huge fan of putting logic into the aspx markup, preferring to have more direct control via methods that i can use 'proper' coding inside (and yes, i know that you can invoke code from the markup as well, but the point being that i don't want to invoke any data access code from the markup where possible). i'm some way down the road in creating a generics/lambda extension that i can use to generate the markup in the background, rather than adding it explicitly in code (i.e. i used to do stuff like currentHtml += "<div id = " + divID + moreCode; etc...)

but anyway, good point about the ODS cache, even if i'll never use it

__________________
jimi

http://www.originaltalent.com

I rewrote the back end to use LINQ before Jim mention it has already been done :(.
I will look at Lee's linq implementation later today.

I used Reflection in the DLL so all the basic functions such as
Create/Update, Delete, GetByID, GetAll, ect could be done without writting any code.

I also moved all the Caching Configuration to the BusinessObjects rather than put them in webconfig. In order for caching to work in the basic DLL functions

Caching is done on server side.
Maybe I am understanding this wrong, but do we need to set a cache duration? Every time there is a change to the database, the cache item is purged out. So why do we need to refresh the data with the cache duration when there has been no changes made to the database?