[infinispan-issues] [JBoss JIRA] (ISPN-4393) Separate Memcached and Hot Rod protocol decoders

[Galder Zamarreño (JIRA)]

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

Galder Zamarreño commented on ISPN-4393:
----------------------------------------

Also, consider using a different base Netty decoder, e.g. ByteToMessageDecoder. See rationale: http://netty.io/4.0/api/io/netty/handler/codec/ReplayingDecoder.html

> Separate Memcached and Hot Rod protocol decoders
> ------------------------------------------------
>
>                 Key: ISPN-4393
>                 URL: https://issues.jboss.org/browse/ISPN-4393
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Remote Protocols
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>
> This is for 7.1, for the first alpha. In 7.0, we've focused on creating Hot Rod 2.0 protocol which adds a lot of enhancements and capabilities in a backwards compatible way.
> In 7.1, a big focus should be on refactoring the protocol decoders for Memcached and Hot Rod which are very entangled and are hindering development of Hot Rod. Essentially, each should have a fully async decoder  that focuses purely on the protocol at hand and makes the most of it.
> This should also enable to improve performance of each protocol decoder.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)