[
https://issues.apache.org/jira/browse/ZOOKEEPER-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979677#comment-16979677
]
Tamas Penzes commented on ZOOKEEPER-102:
----------------------------------------
[~randgalt], no it's not open to all: "If you have an @apache.org email
address, you can [create an account|https://the-asf.slack.com/signup/].";
Not all the contributors/interested parties are committers and without an
Apache e-mail address you cannot reach the ASF Slack.
I would like to have just one question: How do you imagine migrating existing
users/applications to your new solution?
We would need to have an upgrade path, with a step where the old and new
solutions both work if possible.
> 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)
