Tbh, I think I've only seen it in being asked in one case. I don't think it's
top priority.
Galder ZamarreƱo
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
-----Original Message-----
From: jbosscache-dev-bounces(a)lists.jboss.org
[mailto:jbosscache-dev-bounces@lists.jboss.org] On Behalf Of Manik Surtani
Sent: 27 October 2006 13:34
To: jbosscache-dev(a)lists.jboss.org
Subject: [jbosscache-dev] Re: 1.4.0.SP2 or 1.4.1?
Also,
JBCACHE-684 has been made in HEAD - any thoughts on whether this
should be backported to 1.4.x? It is easy enough, and I have seen
people hit this hard limit in eviction queues often enough in support
cases. Galder, thoughts? Is this something a lot of customers would
find helpful in a 1.4 release?
Cheers,
--
Manik Surtani
Lead, JBoss Cache
JBoss, a division of Red Hat
Email: manik(a)jboss.org
Telephone: +44 7786 702 706
MSN: manik(a)surtani.org
Yahoo/AIM/Skype: maniksurtani
On 27 Oct 2006, at 12:31, Manik Surtani wrote:
Brian and I have been speaking about adding JBCACHE-812 to the next
1.4.x release, the purpose being that there may be an AS 4.2.0
release which may allow us to include the MUX.
Since this is a fairly large feature change, I feel it is beyond
the scope of an SP and would warrant a bump up in version numbers.
And TBH, so does JBCACHE-756, since it involves a new JBoss
Serialization jar.
Thoughts on this? Pls respond soon as I hope to cut the next 1.4
release next week.
Cheers,
--
Manik Surtani
Lead, JBoss Cache
JBoss, a division of Red Hat
Email: manik(a)jboss.org
Telephone: +44 7786 702 706
MSN: manik(a)surtani.org
Yahoo/AIM/Skype: maniksurtani
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev