http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660http://hibernatingrhinos.com/open-source/rhino-mockshttp://ayende.com/7169/the-ravendb-caching-solution#comment9http://ayende.com/7169/the-ravendb-caching-solution#comment9Sun, 22 May 2011 08:52:59 GMTI have to say, raccoonblog is clearly *the fastest* serving pages then any other blog engine I've ever seen. It's a great example of the power of RavenDB. All of these great features that RavenDB provides makes a really compelling argument for people to start jumping on board.http://ayende.com/7169/the-ravendb-caching-solution#comment8http://ayende.com/7169/the-ravendb-caching-solution#comment8Sun, 22 May 2011 06:56:03 GMTThere are numerous external links to your (old) site to download Rhino Mocks for Silverlight. Is this port still available for download? I check the 'recent builds' link, but being from the older 3.5 version, it's not in the list. Thanks, Chrishttp://ayende.com/7169/the-ravendb-caching-solution#comment7http://ayende.com/7169/the-ravendb-caching-solution#comment7Fri, 20 May 2011 18:43:06 GMTmeisinger, It checks with the server whenever a query is made, to check if the query result (or the document being loaded) is already in the client cache. The way it work, you'll never get cached information that is out of date.http://ayende.com/7169/the-ravendb-caching-solution#comment6http://ayende.com/7169/the-ravendb-caching-solution#comment6Thu, 19 May 2011 09:07:48 GMTThere's more info on how RavenDB caches doc here http://ayende.com/blog/4748/ravendb-http-cachinghttp://ayende.com/7169/the-ravendb-caching-solution#comment5http://ayende.com/7169/the-ravendb-caching-solution#comment5Wed, 18 May 2011 08:39:46 GMTThat is pretty sweet.http://ayende.com/7169/the-ravendb-caching-solution#comment4http://ayende.com/7169/the-ravendb-caching-solution#comment4Tue, 17 May 2011 23:08:21 GMTmeisinger, iirc it's mostly done through etag caching. Every document gets an etag, which implemented here is a sequential guid. Client sends etag with the request, if they match then raven returns 304 not modified.http://ayende.com/7169/the-ravendb-caching-solution#comment3http://ayende.com/7169/the-ravendb-caching-solution#comment3Tue, 17 May 2011 18:35:43 GMTYes, it is definitely faster!http://ayende.com/7169/the-ravendb-caching-solution#comment2http://ayende.com/7169/the-ravendb-caching-solution#comment2Tue, 17 May 2011 17:25:03 GMTjust a quick question on the cache strategy... i am assuming that client checks with the server to see if the content (or document) has been updated or is out-of-sync; (of course if this assumption is wrong then the question is moot) working with this assumption, does the client actively pull the latest from the server or simply "clear itself out" awaiting the next request? in other words, does the client update the content within the same request or does it simply send what it has currently and upon the next request update itself? just curioushttp://ayende.com/7169/the-ravendb-caching-solution#comment1http://ayende.com/7169/the-ravendb-caching-solution#comment1Tue, 17 May 2011 16:57:25 GMT