3.2 is probably end of year-ish timeframe, depending on what ends up
going in it and holidays, etc.
On Nov 11, 2009, at 11:16 AM, Sergio Bossa wrote:
On Wed, Nov 11, 2009 at 4:51 PM, Alex Miller <amil...@terracottatech.com
> wrote:
Given those alternatives, I'd much rather add a tryLockEntry() :)
Let me
discuss with some people here internally and see whether we can add
this for
the 3.2 release train.
Great, what's the planned release time for 3.2?
I'll leave the interrupt question to Chris (who is out today) since
he just
rewrote the client lock manager. In this case, I think you're
performing a
blocking lock operation so I don't believe it should/would respond to
interrupt.
Okay, I'm adding Chris to this thread.
BTW, you might want to try out some of your perf tests with the
current
trunk - server guys have made some insane improvements in the last
few weeks
in prep for 3.2 plus the new lock mgr is a big improvement,
particularly on
read locks and lock memory footprint.
Very cool: I'll give it a try in a few days.
Thanks for your support,
Cheers,
Sergio B.
--
Sergio Bossa
Software Passionate and Open Source Enthusiast.
URL: http://www.linkedin.com/in/sergiob
_______________________________________________
tc-dev mailing list
tc-dev@lists.terracotta.org
http://lists.terracotta.org/mailman/listinfo/tc-dev
