[
https://issues.apache.org/jira/browse/ZOOKEEPER-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825649#comment-16825649
]
maoling commented on ZOOKEEPER-102:
-----------------------------------
[~belugabehr]
1. Seperate another port for thrift cannot solve the backward compatibility and
will introduce the complexity.
Overall jute cannot communicate with thrift.
2. In the current usage of jute which is only a serialization,not a complete
RPC framework,just like Gson,json....
Before we go further, I am doing an experiment:picking up a api getChildren()
to only replacing it with thrift,then
write a client JMH test to comparing the perfermacne between thrift and jute.
> Need to replace Jute with supported code
> ----------------------------------------
>
> Key: ZOOKEEPER-102
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-102
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: Benjamin Reed
> Priority: Major
> Fix For: 4.0.0
>
>
> ZooKeeper currently uses Jute to serialize objects to put on the wire and on
> disk. We pulled Jute out of Hadoop and added a C binding. Both versions of
> Jute have evolved (although Hadoop still doesn't have a C binding). It would
> be nice to use a more standard serialization library. Some options include
> Thrift or Google's protocol buffers.
> Our main requirements would be Java and C bindings and good performance. (For
> example, serializing to XML would give us incredibly bad performance and
> would not be acceptible!)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
