﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Scooletz commented on RavenDB Aggressive Caching Mode</title><description>Ayende, I agree that it would add additional complexity (as a matter of fact the RavenEtag usage is awsome and it pushes the consistency across network to the limits), but the third point nailed it: not working in all the scenarios, that's a pity. Thx for your explanation.</description><link>http://ayende.com/25601/ravendb-aggressive-caching-mode#comment9</link><guid>http://ayende.com/25601/ravendb-aggressive-caching-mode#comment9</guid><pubDate>Tue, 28 Jun 2011 09:26:34 GMT</pubDate></item><item><title>Ayende Rahien commented on RavenDB Aggressive Caching Mode</title><description>Scooletz,
Yes, it could be made to work, in which case it would:
* Require complex config when running in web farms.
* Complicate explaining how this works.
* We don't have tables, and collections are virtual, it means that in some cases, this wouldn't work.

Rather, it is so much simpler to say that if you care about this, don't use aggressive caching, RavenDB already support HTTP caching, and that is safe from all of those issues.</description><link>http://ayende.com/25601/ravendb-aggressive-caching-mode#comment8</link><guid>http://ayende.com/25601/ravendb-aggressive-caching-mode#comment8</guid><pubDate>Tue, 28 Jun 2011 07:44:51 GMT</pubDate></item><item><title>Scooletz commented on RavenDB Aggressive Caching Mode</title><description>Ok, but I have to ask as I'm curious about your opinion:
using sth like NHibernate UpdateTimestampsCache, storing last modified ETag for each region/document type, wouldn't it work?</description><link>http://ayende.com/25601/ravendb-aggressive-caching-mode#comment7</link><guid>http://ayende.com/25601/ravendb-aggressive-caching-mode#comment7</guid><pubDate>Tue, 28 Jun 2011 06:47:54 GMT</pubDate></item><item><title>Ayende Rahien commented on RavenDB Aggressive Caching Mode</title><description>Schooletz,
Not really, no.
It doesn't make sense, considering most scenarios.
It would be fairly complex to do, too.
Consider the case of me updating a document "users/1" with a new email.

How do I tell a client that has cached the query users by email about that?

How do I even figure this out?</description><link>http://ayende.com/25601/ravendb-aggressive-caching-mode#comment6</link><guid>http://ayende.com/25601/ravendb-aggressive-caching-mode#comment6</guid><pubDate>Mon, 27 Jun 2011 19:05:39 GMT</pubDate></item><item><title>toper commented on RavenDB Aggressive Caching Mode</title><description>yeah.. +1 for that profiler div :) Good stuff!</description><link>http://ayende.com/25601/ravendb-aggressive-caching-mode#comment5</link><guid>http://ayende.com/25601/ravendb-aggressive-caching-mode#comment5</guid><pubDate>Mon, 27 Jun 2011 18:41:51 GMT</pubDate></item><item><title>Chris Wright commented on RavenDB Aggressive Caching Mode</title><description>I see a little div at the top of your blog that says "RavenDB Profiler". Application integration with the profiler is a pretty cool feature, and this is a neat way to demo it.</description><link>http://ayende.com/25601/ravendb-aggressive-caching-mode#comment4</link><guid>http://ayende.com/25601/ravendb-aggressive-caching-mode#comment4</guid><pubDate>Mon, 27 Jun 2011 16:39:59 GMT</pubDate></item><item><title>Scooletz commented on RavenDB Aggressive Caching Mode</title><description>Ayende, speaking about the aggresive caching. Have you considered 'pushing' the invalidation to the clients, via comet or sth?</description><link>http://ayende.com/25601/ravendb-aggressive-caching-mode#comment3</link><guid>http://ayende.com/25601/ravendb-aggressive-caching-mode#comment3</guid><pubDate>Mon, 27 Jun 2011 15:31:26 GMT</pubDate></item><item><title>Ayende Rahien commented on RavenDB Aggressive Caching Mode</title><description>Thanks, 
That was the intent, to make sure that you are well aware of what you are doing.</description><link>http://ayende.com/25601/ravendb-aggressive-caching-mode#comment2</link><guid>http://ayende.com/25601/ravendb-aggressive-caching-mode#comment2</guid><pubDate>Mon, 27 Jun 2011 11:45:27 GMT</pubDate></item><item><title>Scooletz commented on RavenDB Aggressive Caching Mode</title><description>I do like the naming. "Aggressively" makes you think about possibilities of misuse or abuse (as with real anger).</description><link>http://ayende.com/25601/ravendb-aggressive-caching-mode#comment1</link><guid>http://ayende.com/25601/ravendb-aggressive-caching-mode#comment1</guid><pubDate>Mon, 27 Jun 2011 09:04:04 GMT</pubDate></item></channel></rss>