Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aspect Oriented Programming style Caching with Castle Windsor #1

Open
LodewijkSioen opened this issue Dec 11, 2013 · 7 comments
Open
Labels

Comments

@LodewijkSioen
Copy link
Owner

No description provided.

@petermorlion
Copy link

Very cool! Are you thinking about handling cache invalidation or is it not necessary in your case? Would make for a great follow up post (hint hint ;)

@LodewijkSioen
Copy link
Owner Author

Well, it's all academic. We're not actually using this :)

It is possible to give a cache-timeout in the Enterprise Edition on github:

 [Cached(TimeoutInMinutes = 5, CacheKeyGenerator = typeof(DummyCacheKeyGenerator), CacheRegion = "region")]
public virtual DateTime CachedMethodWithSettings(string argumentOne, int argumentTwo)
{    
    return DateTime.Now;
}

@petermorlion
Copy link

Am I correct that the DefaultCacheProvider doesn't check this at the moment?

@LodewijkSioen
Copy link
Owner Author

On line 41 an item is added to the cache with an absolute expiration. The cache implementation itself is responsible for invalidation.

@petermorlion
Copy link

Yes, I'd seen that. Just wasn't sure if I was missing anything. So I understood it correctly. Cool, thanks! Nice, clean implementation by the way!

@LodewijkSioen
Copy link
Owner Author

Thanks! Haven't actually used it though, so it's all just an exercise now.

@petermorlion
Copy link

Exercise is good :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants