I am working on a topic branch off my fork for this, only for the Cassandra
branch. Once it is ready you can have a look at it so that we can work it
out at the core level.
Tristan
On Wed, Dec 1, 2010 at 15:57, Manik Surtani <manik(a)jboss.org> wrote:
Hi Tristan
I have no problem with this being in core, even for 4.2.x. It shouldn't
cause any breakage or issues since core is a dependency of all of the cache
stores anyway.
Re: the marker and strings, I have no problem with this.
Cheers
Manik
On 1 Dec 2010, at 14:54, Tristan Tarrant wrote:
> Dear all,
>
> a user has requested that the Cassandra cache store implement something
akin to the key2stringmapper that the jdbc driver has. Manik has rightly
suggested that we could move the mapper classes from the jdbc cachestore to
a higher level (core ?). While I believe this is 5.0 material, I am planning
to duplicate the system for the Cassandra cachestore for 4.2.x, but I want
to maintain backwards compatibility for users who already have keys. One
thing that the DefaultTwoWayKey2StringMapper does to recognize keys of
different types is that it adds a numeric prefix at the beginning of each
key to determine the type. This is fine for everything else, but I would
like strings to be stored as-is. What do you think if the BOM (Unicode
FEFF), followed by a type identifier, is prefixed at the beginning of each
key when it is not a string ?
>
> Tristan
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev