http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Jean, This is only available on 2.5.http://ayende.com/161377/aggressive-caching-pacified#comment18http://ayende.com/161377/aggressive-caching-pacified#comment18Thu, 28 Mar 2013 21:01:45 GMTI am working on an application using RavenDB, using the latest packages from nuget. I haven't seen this functionality working. Is there anything special that needs to be set for this to work? Thanks.http://ayende.com/161377/aggressive-caching-pacified#comment17http://ayende.com/161377/aggressive-caching-pacified#comment17Thu, 28 Mar 2013 18:56:32 GMTShifatullah, This is attached to the store, not the session. Session are very short lived, and caching stuff on them makes very little sense.http://ayende.com/161377/aggressive-caching-pacified#comment16http://ayende.com/161377/aggressive-caching-pacified#comment16Wed, 27 Mar 2013 08:16:09 GMTSince the functionality being called through store, is cache attached to store or to session? and if we close the session, will it clear the cache?http://ayende.com/161377/aggressive-caching-pacified#comment15http://ayende.com/161377/aggressive-caching-pacified#comment15Wed, 27 Mar 2013 05:07:57 GMTCatalin, But the aggressive caching ISN'T talking to the server.http://ayende.com/161377/aggressive-caching-pacified#comment14http://ayende.com/161377/aggressive-caching-pacified#comment14Tue, 19 Mar 2013 09:18:51 GMTOne definition for "aggressive" is : "deliberately unfriendly behavior involving forcing, constraining or overruling" There's no overruling here being done by the client if the server can invalidate the caches, which means "Aggressive" doesn't seem to be appropriate name in this case. My 2chttp://ayende.com/161377/aggressive-caching-pacified#comment13http://ayende.com/161377/aggressive-caching-pacified#comment13Tue, 19 Mar 2013 09:17:03 GMTAwesome feature. It really sounds like it should be smarter about disconnects, with at least an option to automatically clear the cache - or possibly a smarter way to find out what needs to be cleared. But really, awesome feature.http://ayende.com/161377/aggressive-caching-pacified#comment12http://ayende.com/161377/aggressive-caching-pacified#comment12Tue, 19 Mar 2013 00:16:38 GMTSo is the API for using aggressive caching still the same with the exception of being able to use a longer timeout?http://ayende.com/161377/aggressive-caching-pacified#comment11http://ayende.com/161377/aggressive-caching-pacified#comment11Mon, 18 Mar 2013 17:31:26 GMT@Darius Because Raven also includes automatic caching of all documents. If you request a document that already exists in cache, Raven will tell the server "I would like this document, but I already have version X in my cache" using the standard HTTP mechanics of passing the last modified date. If the document has not been modified, the server will send back a 304 Not Modified, and the client will give you back the cached version. So that is the "normal" caching, and the "aggressive" caching is the additional choice to skip talking to the server at all. @Ayende, this is AWESOME by the way, thank you!http://ayende.com/161377/aggressive-caching-pacified#comment10http://ayende.com/161377/aggressive-caching-pacified#comment10Mon, 18 Mar 2013 13:39:54 GMTLol, why the word aggressive? :) It doesn't add anything, it's still just normal caching. I'd go with simpler using (session.Advanced.DocumentStore.CacheFor.Minutes(5)) or smth similar.http://ayende.com/161377/aggressive-caching-pacified#comment9http://ayende.com/161377/aggressive-caching-pacified#comment9Mon, 18 Mar 2013 13:15:25 GMTHarry, Yes, that is available in the API.http://ayende.com/161377/aggressive-caching-pacified#comment8http://ayende.com/161377/aggressive-caching-pacified#comment8Mon, 18 Mar 2013 11:29:17 GMTIs there some way you can hook into the disconnection event so you could opt in to invalidate-on-disconnect?http://ayende.com/161377/aggressive-caching-pacified#comment7http://ayende.com/161377/aggressive-caching-pacified#comment7Mon, 18 Mar 2013 11:28:52 GMTMāris, For cases where you have actual disconnection. Note that we also have just AggressiveCache() method.http://ayende.com/161377/aggressive-caching-pacified#comment6http://ayende.com/161377/aggressive-caching-pacified#comment6Mon, 18 Mar 2013 11:03:23 GMTIf server sends notifications about changes, why cache duration is needed? If cache is expired application will be notified.http://ayende.com/161377/aggressive-caching-pacified#comment5http://ayende.com/161377/aggressive-caching-pacified#comment5Mon, 18 Mar 2013 11:00:11 GMTHarry, No, the client will try to reconnect automatically. But it is a possibility, that is why it is still an active decision on your part.http://ayende.com/161377/aggressive-caching-pacified#comment4http://ayende.com/161377/aggressive-caching-pacified#comment4Mon, 18 Mar 2013 10:42:52 GMTNow that sounds good. If the client is disconnected, is the cache cleared automatically? (i.e. is there any way the client could miss the notification?)http://ayende.com/161377/aggressive-caching-pacified#comment3http://ayende.com/161377/aggressive-caching-pacified#comment3Mon, 18 Mar 2013 10:35:36 GMTDario, Evict what?http://ayende.com/161377/aggressive-caching-pacified#comment2http://ayende.com/161377/aggressive-caching-pacified#comment2Mon, 18 Mar 2013 10:26:03 GMTWhy there is no 'evict'?http://ayende.com/161377/aggressive-caching-pacified#comment1http://ayende.com/161377/aggressive-caching-pacified#comment1Mon, 18 Mar 2013 10:23:39 GMT