Re: [VETO] Re: [jcs] What's next?

2014-05-22 Thread Thomas Vandahl
Hi Romain, sorry, I only find time to look at my mail once a week. On 16.05.14 23:40, Romain Manni-Bucau wrote: Hi Thomas, is it an old mail or not? It is not. If not can you detail the changes you dislike please? - Removing Serializable from the key and value types. This is required for

Re: [VETO] Re: [jcs] What's next?

2014-05-22 Thread Romain Manni-Bucau
About serializable: that's fine but doesn't have to be forced in the API since auxilaries can not mandate it. Another point is cache elements have a serializer and if you set it you don't want to use java serialization (json typically) so if it is still mandatory we should get rid of it IMHO.

Re: [VETO] Re: [jcs] What's next?

2014-05-22 Thread Thomas Vandahl
On 22.05.14 19:24, Romain Manni-Bucau wrote: About eviction: is it still the case? Thought I removed it when merged with jcs backend I have no idea. I lost track when I needed to merge my changes with your reformatted imports (That was one thing I forgot). Why was that necessary? Not sure I

Re: [VETO] Re: [jcs] What's next?

2014-05-22 Thread Romain Manni-Bucau
well Now JCache is based on JCS so think almost all comments are no more relevant. Well if commons can't support module (jcs wouldn't be the first BTW) I have no issue moving it outside of commons. This is quite common actually. The point about remote mode is it is not as easy as alternatives

Re: [VETO] Re: [jcs] What's next?

2014-05-22 Thread Phil Steitz
On 5/22/14, 12:45 PM, Romain Manni-Bucau wrote: well Now JCache is based on JCS so think almost all comments are no more relevant. Well if commons can't support module (jcs wouldn't be the first BTW) I have no issue moving it outside of commons. This is quite common actually. This bothers me