Hi Jason,

I have developed a redis cache store which has now been completed and released under the infinispan org as part of version 8, available through central.

I had begun to look at what changes would be required under wildfly. I have made changes to the xml reader and writer for config for a concrete redis-store type but haven't worked out how to update the web ui and cli.

This got me thinking as to whether a concrete config tag is required at all since there is always the custom store.

Therefore, I thought I'd check. What changes should I be developing to make my redis integration in to wildfly 10?

Thanks
Simon

Sent from my iPhone

On 28 Jul 2015, at 21:22, Jason Greene <jason.greene@redhat.com> wrote:


On Jul 28, 2015, at 3:04 PM, Simon Paulger <spaulger@codezen.co.uk> wrote:

Hi,

My company uses JBoss AS 7 (before Wildfly I know). We also use Redis cache store for PHP stacks and I'd like to be able to do the same for Wildfly (I'm considering upgrade paths).

I see there is an old JIRA enhancement issue raised here: https://issues.jboss.org/browse/ISPN-3465

I was wondering what the appetite for creating a Redis cache store is. If this were something I were to develop in both inifinispan and wildfly, would it be well received by the JBoss community?

Hi Simon, 

Thanks for the interest, and it sounds great to me! 

I would recommend starting by posting to infinispan-dev your interest in the feature (if you haven’t already), and they can help you get started. I would imagine the infinispan memcached code is a good starting point, and may in fact be adaptable to the Redis protocol, perhaps by forking it.

One thats done there is some integration bits on the WildFly side, but I wouldn’t worry about that until its shipped in an infinispan release.

Thanks,
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat