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.
About eviction: is it still the case? Thought I removed it when merged with jcs backend Not sure I get your point about removing network/remote features, never said we should remove it but we shouldn't have it by default for JCache. JCache uses JCS so once again not sure I follow. Finally extra module is quite useful when you use JCache and that's what we do in all "EE" projects cause this module doesn't depend on the implementation. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-05-22 19:18 GMT+02:00 Thomas Vandahl <t...@apache.org>: > 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 almost all auxiliaries to work. > - Implementing eviction methods that already exist. > - Planning to remove network functionality from JCS. > - Planning to remove RemoteCache. > - Adding extras modules that have nothing to do with caching > - Removing JCS from the JCache extension completely. > > Anything I forgot? > > Bye, Thomas. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
