Comments on: Agatha’s Caching Layer Implementation: First Draft

By: Agatha 1.1 Is Out | The Inquisitive Coder – Davy Brion's Blog

Agatha 1.1 Is Out | The Inquisitive Coder – Davy Brion's Blog — Sun, 09 May 2010 12:09:19 +0000

[...] version of the server side caching layer. Consider this implementation to be experimental and there are most likely plenty of issues [...]

By: Checking Whether A Method Is Overridden | The Inquisitive Coder – Davy Brion's Blog

Mon, 11 Jan 2010 20:05:09 +0000

[...] of the requirements for using Agatha’s Caching Layer is that your request types must override the Equals and the GetHashCode methods. In order to [...]

By: How QuickNet Found 2 Bugs That You And I Didn’t | The Inquisitive Coder – Davy Brion's Blog

Tue, 22 Dec 2009 22:03:51 +0000

[...] Agatha’s Caching Layer Implementation: First Draft [...]

By: Interesting Finds: 2009 12.15 ~ 12.20 - gOODiDEA.NET

Interesting Finds: 2009 12.15 ~ 12.20 - gOODiDEA.NET — Sun, 20 Dec 2009 00:35:15 +0000

[...] Agatha’s Caching Layer Implementation: First Draft [...]

By: Davy Brion

Davy Brion — Tue, 15 Dec 2009 05:49:01 +0000

@Marco,

we can’t use a container-specific feature…

By: Marco

Marco — Tue, 15 Dec 2009 04:09:53 +0000

Sounds like the windsor interceptor would work well in this situation.

By: Andrew Rea

Andrew Rea — Mon, 14 Dec 2009 12:52:20 +0000

Nice post, I got thinking about the caching aspect after reading a few of your earlier posts. I had an idea about creating a custom behaviour which you could for example use as an attribute to decorate the method. Inside the behaviour, think it is a dispatcher, not sure, but anyway you could use the as keyword to check that the incoming type is of ICacheable or something:


var cacheRequest = request as ICacheable;

if(cacheRequest != null){

return cacheRequest.HandleCaching(); //Or something

}

Anyway, just a thought. I am really enjoying your posts on your Agatha project!! Excellent work and keep it up!!

By: Davy Brion

Davy Brion — Mon, 14 Dec 2009 10:38:04 +0000

@Kilfour

ah, thanks for the timer tip

as for the testability of the timer… i suspect a timer wrapper will make its way into the codebase soon enough

and about overriding Equals and GetHashCode, it should indeed be checked at configuration time

By: kilfour

kilfour — Mon, 14 Dec 2009 10:35:29 +0000

It works, apart from a minor detail : ‘new Timer(expiration.Milliseconds);’ should be ‘new Timer(expiration.TotalMilliseconds);’.

The use of the inner Timer makes it really hard to test though.

‘your requests which enable response caching must override the Equals and GetHashCode() methods correctly’
This might be a source of hard to track down bugs. Maybe Agatha could verify this at configuration time ?