[infinispan-issues] [JBoss JIRA] (ISPN-5342) Refactor Hot Rod server code

[Gustavo Fernandes (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gustavo Fernandes updated ISPN-5342:
------------------------------------
    Description: 
This should include:

* Use ByteToMessageDecoder rather than ReplayDecoder
*  Decouple Decoder/Encoder from cache/exec operations invocation and channel IO related tasks. Decoder/Encoders should deal only with Bytes to Messages transformations, and could be possibly re-used in a eventual Netty Client
* Define more clearly Hot Rod Requests and Responses objects, and add a channel handler to operate on those messages by invoking cache or scripts operations
* Better separation version-wise of the DecoderXX/EncoderXX, avoiding using a single class for multiple versions

  was:
This should include:

* Use ByteToMessageDecoder rather than ReplayDecoder
*  Decouple Decoder/Encoder from cache/exec operations invocation and channel IO related tasks. Decoder/Encoders should deal only with Bytes to Messages transformations, and could be possibly re-used in a eventual Netty Client
* Define more clearly Hot Rod Requests and Responses objects, and add a channel handler to operate on those messages by invoking cache or scripts operations
* Better separation version-wiser of the DecoderXX/EncoderXX, avoiding using a single class for multiple versions



> Refactor Hot Rod server code
> ----------------------------
>
>                 Key: ISPN-5342
>                 URL: https://issues.jboss.org/browse/ISPN-5342
>             Project: Infinispan
>          Issue Type: Task
>          Components: Server
>    Affects Versions: 7.2.0.Beta2
>            Reporter: Gustavo Fernandes
>
> This should include:
> * Use ByteToMessageDecoder rather than ReplayDecoder
> *  Decouple Decoder/Encoder from cache/exec operations invocation and channel IO related tasks. Decoder/Encoders should deal only with Bytes to Messages transformations, and could be possibly re-used in a eventual Netty Client
> * Define more clearly Hot Rod Requests and Responses objects, and add a channel handler to operate on those messages by invoking cache or scripts operations
> * Better separation version-wise of the DecoderXX/EncoderXX, avoiding using a single class for multiple versions



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)