Last post Oct 26, 2008 08:14 AM by pure.krome
Oct 26, 2008 02:04 AM|pure.krome|LINK
I'm wondering where you would place caching into the project. So for example, imagine we want to cache the products. Would you guys consider caching methods on contollers or maybe throw certain things into a System.Web.Cache .. and maybe have these things
in the Service project?
i'm interested to see how you guys would value-add caching to the storefront.
Oct 26, 2008 02:27 AM|H_R|LINK
You can cache objects as well as user controls and pages, in fact it depends on what you need to be cached, sometimes it seems to be reasonable to cache a user control as it is used in many pages and it contains
info that are not supposed to change for a while, on the other hand you might need to cache an object or even a string ! for example you can cache a data table to reduce you trance actions with your database
Caching is not complicated at all ! with a little bit of googling you can find how to practically use it
Oct 26, 2008 08:14 AM|pure.krome|LINK
dude - i think u misinterpretted what i ment. I know all about caching, what can be cached and how, etc.
I was curious to see if caching was going to be implimented into this kit and if so, how? page output caching, with donuts (with the user info being cut out) ? or object caching, like caching the products or orders. If so, then where will this be added?
to the service layer? or on the mvc app layer, with some custom model's or something? I know this can be done many ways and various places .. but this is a KIT and i'm hell-interested to see what Rob decides to do :)