On 11-04-01 11:54 AM, Galder Zamarreño wrote: > Hi, > > Re: https://issues.jboss.org/browse/ISPN-986 > > As indicated in my comments, there's two room for two types of serialization > mechanisms: one for end users and the other for SPIs. > > I've got a solution for this in > https://github.com/galderz/infinispan/commit/09096f7998c0d0a5aae76d55bf59c72fe1cb510e > and wanted to give a heads up to everyone on what it involves: > > - Two separate externalizer interfaces: Externalizer (which currently, to > disrupt as little code as possible, is named EndUserExternalier) and > ExternalizerSpi or ServiceProviderExternalizer (currently named > Externalizer). The first API is basic read/write methods and the second one > with a couple of more methods for more specialised behaivour. Do people like > these names? Or can someone come up with better names? More detailed info on > the use cases in the JIRA.
I say forget disrupting little code as possible as a guideline, lets integrate a solution with these automatically installed Externalizers that you mention in the JIRA. I bet you most users will love and only need that. OTOH current mechanism should stay in place for both SPIs and regular super users willing to put an effort and squeeze out every bit of performance. _______________________________________________ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev
