On 8 Dec 2011, at 15:10, Paolo Romano wrote:
On 12/6/11 11:46 AM, Galder ZamarreƱo wrote:
> Hi,
>
> Re:
https://github.com/infinispan/infinispan/pull/697#r272846
>
> When in place, I'd like to use the ability to provide a version externally with
Hibernate in order get versions to come from Hibernate.
>
> As indicated by
http://community.jboss.org/wiki/VersioningDesignDocument, this would
enable other Hibernate Cache concurrency strategies to be supported which are not
necessarily transactional/
I'm not an expert on Hibernate cache strategies but this seems a
relevant use case.
>
> So, opening the debate, would it make sense for versioning to work also with non
transactional environments?
Sorry for replying with another question: are you planning to keep on
supporting both versioning and non-versioning data containers in
transactional mode?
I think yes. There is an overhead in maintaining versions (additional memory, larger
payloads to RPCs since versions need to be propagated, etc). So in certain cases if the
application can deal with last-commit-wins, not using versions is a valid use case.
My 2 cents are that once versioning is well tested and optimized the
code base would probably be simplified if eventually it supported only
versioning... that would also simplify our work to re-base the
transactional replication/distribution protocols that we've been
developing so far ;-)
Cheers,
Paolo
_______________________________________________
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