Re: [infinispan-dev] TxRecovery design update

In fact, if you do what I suggest, you don't need the following: recoveryInfoCacheName="recoveryCache" Or at least what you could do is this: - If recoveryInfoCacheName is defined, use that cache configuration after validating that it fulfills minimum requirements, i.e has passivation enabled...etc. - If recoveryInfoCacheName not defined, define it programmatically with the correct expected settings. This way you get best of both worlds. Users are not forced to define the recovery cache, hence you avoid potential user configuration errors (i.e. forgetting to define the cache in the first place), while at the same time, people can define the cache to further tweak it, i.e. tweak lock timeout, expiration time...etc. This is probably the strategy I should have followed for the Hot Rod topology cache, but instead went for option that fully hides away the topology cache, and can only be tweaked via particular parameters. On Mar 14, 2011, at 10:57 AM, Galder Zamarreño wrote: -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache