Hi,
I've started working on the 2nd level cache implémentation for NHibernate.
Thanks to the test base, it runs just fine and appfabric is a very
descent and stable cache engine (in perf, we are equivalent to ncache).
However, I have some technical questions :
- The DataCacheFactory (establishing the socket btw the client and the
host) seems to be recommended as a singletion implementation. In this
situation, I'm also using the cache for other requirements
(notification, object repository...).
This means that for one instance of my application, the pattern required
by ms (I assume for avoiding deadlock) has to produce a cache to
implements the required ICache for Nh, and the required functionality
I'd likely be using. I was thinking of a ICacheExtension, but it would
require a binding to NHibernate in domains that are not supposed to use
it. My other option would be to create an AppFabric factory that could
handle the datacache factory, and use Ioc to locate the factory in
Nhcache or in another application.
- The lock/unlock process is handled through the production of an
DataCacheHandle created each time you lock an item and used to identify
the item you need to unlock. Here, my question would be : in a
distributed scenario (serveral app server using the same cache,the same
db, but with one hibernate implement per app server) how could I handle
this situation ?
Do someone has more input on the importance of the Datacachehandle ???
There is very few information on it.
- I'd love to release it to the community, but since it is a
contribution, I think that I have to find a solution to this items,
because I think they are key point.
I'm looking for ideas and solution. I'm open to any suggestion.
--
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/nhusers?hl=en.
