Hi,

I'm writing an application that will be deployed as a thick-client (NHibernate deployed on the client). The application consists of a number of loosely coupled components that access data independently which is somewhat inefficient.

Therefore I would like to use a process-wide 2nd-level cache. However, the SysCache seems targeted towards web applications, and I've read that the Prevalence cache is very slow (http://forum.hibernate.org/viewtopic.ph ... ence+cache).

Are there any cache implementations suitable for a thick-client?

Also, in the docs it says:



Does this mean that you can specify the cache globally, rather than on a per class/collection basis?

Thanks,
jr

You can use SysCache on winforms, it will work fine on 2.0 (1.1 should work, but not a supported scenario by MS).

Another option is to use the Caching AppBlock, which also saves to disk, which may be better as far as you are concerned.

The <class-cache> <collection-cache> are generally used to put all the cache definations in one file, instead of having them all over the place.

Just a note, if you want to use the Caching AppBlock, you would need to write an adapter for NH to use it, there isn't one currently.

Thanks, I'll try SysCache then, and maybe try writing an adapter for the Caching AppBlock at some point.

Could anyone please tell me why the default Hashtable cache is not recommended for production use, even in smaller rich client applications?
Does it lack features (expiry, ...) or stability (memory, thread-safety, ...)?

Or is the 'not recommended' part targetted at web applications rather than (single threaded) rich clients with nhibernate deployed to the desktop?

Thread safety,mainly.
It is also a memory leak, because stuff never goes out unless explicitly evicted.

Yeah, that's what I suspected; thanks for the info Ayende.

There is a cache implementation built around memcached you might want to try. It is in the Beta1 download, or you can compile from the trunk.