[infinispan-issues] [JBoss JIRA] Commented: (ISPN-29) Cache server and client module

Manik Surtani (JIRA) jira-events at lists.jboss.org
Tue Jul 7 09:58:51 EDT 2009


    [ https://jira.jboss.org/jira/browse/ISPN-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12475212#action_12475212 ] 

Manik Surtani commented on ISPN-29:
-----------------------------------

Just to clarify, as far as memcached is concerned the goal is to write a server module.  Not a client.  The server module would wrap an Infinispan Cache instance, and would be used with any other memcached client library, be it in Java, Python, etc.

I know the subject of this JIRA is a little far-reaching, but in reality it should be broken down into a few different subtasks.

Regarding your points above:

#1 we would want to use our own locking.  This is where, to a large degree, our strength lies.  I haven't looked at the memcached proto in detail yet, but if it supports atomic calls then thats what the client should use, and delegate the atomicity to the server side.  Infinispan's Cache extends ConcurrentMap so you should have all you need here.

#2 Infinispan's Cache supports lifespans, ttls, etc in its API.  As long as this is a part of the protocol it can be translated easily enough.

#4  We just want flexibility.  Either way the transport needs to be pluggable so we can use XNIO/Netty/MINA/your homerolled JNI comms module using libaio/JDK7 NIO2/whatever.  Picking XNIO to start with since we are familiar with it and it too is a JBoss project, other transports may evolve as and when.

#6  Yes I know - it was written as a demo.  It cannot be the basis of a full impl.

#8  Nothing.  Just that the last thing I want is to yank in yet another unnecessary dependency.  



> Cache server and client module
> ------------------------------
>
>                 Key: ISPN-29
>                 URL: https://jira.jboss.org/jira/browse/ISPN-29
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Cache Server
>            Reporter: Manik Surtani
>            Assignee: Galder Zamarreno
>             Fix For: 4.1.0.BETA1, 4.1.0.GA
>
>
> To be built on top of the cache.
> Transports should be pluggable - Apache MINA, Netty, JDK7 NIO2, native, etc., but for now just build one based on XNIO
> Protocols should be pluggable - memcached text-based, custom binary with server topology information
> Test with various memcached clients (java and non-java)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the infinispan-issues mailing list