[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979129#comment-16979129
 ] 

Zili Chen commented on ZOOKEEPER-102:
-------------------------------------

Hi [~randgalt] & [~eribeiro] for the workflow I think transform this JIRA into 
an umbrella issue and kick off a series of subtasks is a good beginning. IIRC 
ZK has a dedicate Gitter channel we can make use of; besides we can synchronize 
significant decision on JIRA or design document.

Here are a few questions:

1. As described by [~randgalt], we don't keep backward compatibility in this 
effort. I agree and second that "If Jute classes are retained, there's nothing 
more to do refactoring-wise". However, this requires a community consensus 
anyway.

2. For the form we check in code, shall we start a branch towards this big 
refactor in apache/flink repo, collaborate on that branch and eventually merge 
into 4.x branch(or itself be).

3. As I mentioned above, there are still a few of users who develop their 
application on c-client, which means this effort also breaks such users setup.

Of course I'm glad to help on this effort!

> 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
>            Assignee: Jordan Zimmerman
>            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
(v8.3.4#803005)

Reply via email to