Thanks - I 'll look at this and give you feedback.
Re:github, you only need an account and fork from our repo. More on it here:
http://community.jboss.org/wiki/InfinispanandGitHub
github is a grate tool for code-review as well.
Cheers,
Mircea
On 18 Feb 2011, at 13:30, Sebastiano Peluso wrote:
Hi Mircea Markus,
we are sorry for this late reply but we spent some time to "clean"
the code :-) .
> Is this propagation taking place in transaction's scope? Or after the transaction
is completed locally? If later, you do propagate changes to other nodes async (this would
leave place to consistency issues)?
This propagation takes place in transaction's scope just like the
prepare phase in the current Infinispan's replication scheme. Update
brodcast is synchronous in such a way we cannot have consistency issues
(now we suppose a failiure-free environment).
> This looks good to me. I would expect all the tests suite to pass. Is this code
accessible somewhere(both ISPN and Radargun code)? I'd love to give it a look.
You can donwload the two implementations at:
http://www.gsd.inesc-id.pt/~peluso/infinispan/infinispan.tar.bz2
http://www.gsd.inesc-id.pt/~didona/Radargun/radargun.tar.bz2
We made a clone of the Infinispan code from github two weeks ago
(creating a breanch in local) and we would like to make a fork of the
current snapshot on github, in order to perform a push operation on the
resulting snapshot. How can we make the aforementioned fork? Do we only
need an account there?
> Thank you!
Thank you too!!!
Regards,
Sebastiano Peluso, Diego Didona
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev