Didn't I just say exactly that ? I don't understand where we differ. Tristan
On 03/20/2013 12:25 PM, Sanne Grinovero wrote: > Why would you need to *store* anything which is equal for all entries? > I'd have an interceptor "decorate" stuff with some constant additions; > otherwise you could also think of reusing instances, like I had > suggested a while back to change the Externalizer contract to allow it > to be passed some context to make unique objects taking them from a > pool. > > At least it looks like you would have to split such metadata: version > for example needs to be maintained per entry, as will be vector > clocks. > > Sanne > > On 20 March 2013 11:04, Tristan Tarrant <[email protected]> wrote: >> On 03/20/2013 11:51 AM, Manik Surtani wrote: >>> On 18 Mar 2013, at 12:21, Galder Zamarreño <[email protected]> wrote: >>> >>>> IOW, you'll be able to say: create an Infinsipan Server that has String as >>>> key and value of type X, where X is the actual data type, no metadata!! >>>> The metadata (version, encoding, whatever is requried to fulfill the >>>> compatibility reqs in ISPN-2281) will be passed as part of the >>>> put/replace…etc (I will email this around when in place). >>> Not sure I get this. Where will this metadata be stored? >> Metadata should be moved to the ICE-level, or the Cache-level (for >> metadata common to all entries in the cache, to save space: e.g. if all >> entries in my cache are text/plain) >> >> Tristan >> _______________________________________________ >> infinispan-dev mailing list >> [email protected] >> https://lists.jboss.org/mailman/listinfo/infinispan-dev > _______________________________________________ > infinispan-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/infinispan-dev _______________________________________________ infinispan-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/infinispan-dev
