Upgrade to JR 2.1.2

[Ian Boston <ie...@tfd.co.uk>]

WDYT?
2.1.2 was released to fix concurrency issues.
Although my code base (Nakamura) cant easily upgrade because we added some desperate (and ugly) patches,  I think it would be a big benefit to Sling and others who have deny permissions in their repository and either highly concurrent reads or concurrent writes.

This should obviously wait till the JCR Access Managers are released, as there could be an impact there.
Ian

Re: Upgrade to JR 2.1.2

[Mike Moulton <mi...@meltmedia.com>]

There is also a nasty DB connection leak fix from my team in JR 2.1.2.

+1 - non binding.


On Nov 4, 2010, at 3:04 AM, Ian Boston wrote:

> WDYT?
> 2.1.2 was released to fix concurrency issues.
> Although my code base (Nakamura) cant easily upgrade because we added some desperate (and ugly) patches,  I think it would be a big benefit to Sling and others who have deny permissions in their repository and either highly concurrent reads or concurrent writes.
> 
> This should obviously wait till the JCR Access Managers are released, as there could be an impact there.
> Ian

Re: Upgrade to JR 2.1.2

[Justin Edelson <ju...@gmail.com>]

On 11/4/10 6:04 AM, Ian Boston wrote:
> This should obviously wait till the JCR Access Managers are released, as there could be an impact there.
This was basically my thought as well.

Justin

Re: Upgrade to JR 2.1.2

[Felix Meschberger <fm...@gmail.com>]

+1

Regards
Felix

Am Donnerstag, den 04.11.2010, 10:04 +0000 schrieb Ian Boston: 
> WDYT?
> 2.1.2 was released to fix concurrency issues.
> Although my code base (Nakamura) cant easily upgrade because we added some desperate (and ugly) patches,  I think it would be a big benefit to Sling and others who have deny permissions in their repository and either highly concurrent reads or concurrent writes.
> 
> This should obviously wait till the JCR Access Managers are released, as there could be an impact there.
> Ian