[
https://issues.apache.org/jira/browse/THRIFT-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624424#action_12624424
]
Pete Wyckoff commented on THRIFT-110:
-------------------------------------
> We will have to keep a close track of how the other protocol is making use of
> certain 'bits' and we will have to resort to very clever tricks to work
> around. T
protobuf's binary protocol is probably stable. I doubt it is being changed. And
the best way to make interoperability happen is always to use their libraries
themselves, licensing issues aside. Interoperability give's protobuf's users
backwards compatibility when using thrift, a big thing towards adopting it in
addition to getting all the other languages. i.e., thrift would be a proper
superset.
> A more compact format
> ----------------------
>
> Key: THRIFT-110
> URL: https://issues.apache.org/jira/browse/THRIFT-110
> Project: Thrift
> Issue Type: Improvement
> Reporter: Noble Paul
>
> Thrift is not very compact in writing out data as (say protobuf) . It does
> not have the concept of variable length integers and various other
> optimizations possible . In Solr we use a lot of such optimizations to make a
> very compact payload. Thrift has a lot common with that format.
> It is all done in a single class
> http://svn.apache.org/viewvc/lucene/solr/trunk/src/java/org/apache/solr/common/util/NamedListCodec.java?revision=685640&view=markup
> The other optimizations include writing type/value in same byte, very fast
> writes of Strings, externalizable strings etc
> We could use a thrift format for non-java clients and I would like to see it
> as compact as the current java version
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
