You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2013/02/26 15:50:13 UTC

[jira] [Updated] (BOOKKEEPER-576) Bookie client should use netty Decoder/Encoder

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Kelly updated BOOKKEEPER-576:
----------------------------------

    Attachment: 0002-BOOKKEEPER-576-Bookie-client-should-use-netty-Decode.patch
    
> Bookie client should use netty Decoder/Encoder
> ----------------------------------------------
>
>                 Key: BOOKKEEPER-576
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-576
>             Project: Bookkeeper
>          Issue Type: Sub-task
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>             Fix For: 4.3.0
>
>         Attachments: 0002-BOOKKEEPER-576-Bookie-client-should-use-netty-Decode.patch
>
>
> Current it encodes and decodes in an adhoc manner in PerChannelBookieClient. It would be better to have the request encoding and decoding in the same place and it should also be done with a OneToOne*coder like is done with the server. 
> This will make it easier to add a versioning decoder, which will make it much easier to extend the bookie protocol.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira