It isn't that easy to set up though - since the CacheImpl is constructed very early on
and the transaction attributes can be added later before starting the cache.
On 22 Nov 2011, at 18:10, Mircea Markus wrote:
Mainly what is transaction related, i.e. the autoCommit
functionality.
On 22 Nov 2011, at 11:02, Manik Surtani wrote:
> What functionality do you want to split out between the two impls?
>
> On 22 Nov 2011, at 08:13, Dan Berindei wrote:
>
>> Any pros?
>>
>> On Tue, Nov 22, 2011 at 2:11 AM, Mircea Markus <mircea.markus(a)jboss.com>
wrote:
>>> This is simple to implement and I don't see how it can cause any API
incompatibilities, but as it is in the very core I'd like to ask your opinion - any
cons for adding it into next release?
>>> _______________________________________________
>>> infinispan-dev mailing list
>>> infinispan-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>>
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
> --
> Manik Surtani
> manik(a)jboss.org
>
twitter.com/maniksurtani
>
> Lead, Infinispan
>
http://www.infinispan.org
>
>
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev